CVE-2022-36883
highpriority · track · 42OT risk · elevatedEPSS 0.070 · 94 %ileexploit · PoCDEEURUUSEPSS · scored 2026-10-27
A missing permission check in Jenkins Git Plugin 4.11.3 and earlier allows unauthenticated 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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5.5–7.5
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (1)
Public proof-of-concept and weaponised exploit code.
- superjimmygou/CVE-2022-36883superjimmygou/CVE-2022-36883PoC · poc_in_github
affected products (6)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2022-0852Jenkins: Mehrere SchwachstellenDeutsch2022-07-27csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Jenkins ausnutzen, um einen Cross Site Scripting oder CSRF Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen, Informationen offenzulegen oder Daten zu manipulieren
- GHSA-v878-67xw-grw2Lack of authentication mechanism in Jenkins Git Plugin webhook2022-07-28ghsa · osvUS
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. In addition to this basic functionality, the endpoint also accept a `sha1` parameter specifying a commit ID. If this parameter is specified, jobs configured with the specified repo will be triggered immediately, and the build will check out the specified commit. Additionally, the output of the webhook endpoint will provide information about which jobs were triggered or scheduled for polling, including jobs the user has no permission to access. This allows attackers with knowledge of Git repository URLs to trigger builds of jobs using a specified Git repository and to cause them to check out an attacker-specified commit, and to obtain information about the existence of jobs configured with this Git repository. 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](https://github.com/jenkinsci/git-plugin/#push-notification-from-repository).
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (11)
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2022/07/27/1cnnvd
- https://cxsecurity.com/cveshow/CVE-2022-36883/cnnvd
- https://packetstormsecurity.com/files/170511/Red-Hat-Security-Advisory-2023-0017-01.htmlcnnvd
- https://packetstormsecurity.com/files/170929/Red-Hat-Security-Advisory-2023-0560-01.htmlcnnvd
- https://vigilance.fr/vulnerability/Jenkins-Plugins-multiple-vulnerabilities-38933cnnvd
- https://www.auscert.org.au/bulletins/ESB-2022.3676cnnvd
- https://www.jenkins.io/security/advisory/2022-07-27/#SECURITY-284cnnvd
- http://www.openwall.com/lists/oss-security/2022/07/27/1enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan