Build triggering via unauthenticated GET webhook
Published Jul 27, 2022 · Updated Aug 3, 2024
CSRF in Jenkins Git Plugin 4.11.3 and earlier allows remote attackers to trigger builds that check out a chosen commit. The /git/notifyCommit webhook accepts unauthenticated GET requests and uses attacker-supplied url and sha1 parameters to select matching jobs and the commit built. Exploitation requires a user to load a crafted request and knowledge of a configured repository URL; the resulting build is limited to jobs using that repository.
Summary
What happened
CSRF in Jenkins Git Plugin 4.11.3 and earlier allows remote attackers to trigger builds that check out a chosen commit. The /git/notifyCommit webhook accepts unauthenticated GET requests and uses attacker-supplied url and sha1 parameters to select matching jobs and the commit built. Exploitation requires a user to load a crafted request and knowledge of a configured repository URL; the resulting build is limited to jobs using that repository.
The record
- CVE
- CVE-2022-36882
- Published
- Jul 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Git Plugin
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=4.11.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo