Lack of authentication mechanism in Jenkins Git Plugin webhook

高 8.8CVE-2022-36882 · GHSA-8xwj-2wgh-gprh · 27/07/2022 公開 · 17/06/2026 更新

要点

CVE-2022-36882 は org.jenkins-ci.plugins:git, git (jenkins) に影響する深刻度「高」 (CVSS 8.8) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.74%（全脆弱性の 54.6% より高い）。
対処：4.11.4 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
org.jenkins-ci.plugins:git Maven	`< 4.11.4`	`4.11.4`
git jenkins	`≤ 4.11.3`	修正版なし

概要

Git Plugin provides a webhook endpoint at /git/notifyCommit that can be used to notify Jenkins of changes to an SCM repository. For its most basic functionality, this endpoint receives a repository URL, and Jenkins will schedule polling for all jobs configured with the specified repository. In Git Plugin 4.11.3 and earlier, this endpoint can be accessed with GET requests and without authentication.

This webhook endpoint does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Git Plugin 4.11.4 requires a token parameter which will act as an authentication for the webhook endpoint. While GET requests remain allowed, attackers would need to be able to provide a webhook token. For more information see the plugin documentation.

NVD の説明

A cross-site request forgery (CSRF) vulnerability in Jenkins Git Plugin 4.11.3 and earlier allows attackers to trigger builds of jobs configured to use an attacker-specified Git repository and to cause them to check out an attacker-specified commit.