Build triggering via CSRF-enabled GET endpoint
Published Jan 12, 2022 · Updated Aug 3, 2024
Cross-site request forgery in Jenkins 2.329 and earlier and LTS 2.319.1 and earlier allows remote attackers to trigger parameterless jobs. The manual-build HTTP endpoint accepts a state-changing GET request instead of requiring POST when no security realm is configured. A victim must load attacker-controlled content that submits the request, and the result is limited to starting an existing job that requires no parameters.
Summary
What happened
Cross-site request forgery in Jenkins 2.329 and earlier and LTS 2.319.1 and earlier allows remote attackers to trigger parameterless jobs. The manual-build HTTP endpoint accepts a state-changing GET request instead of requiring POST when no security realm is configured. A victim must load attacker-controlled content that submits the request, and the result is limited to starting an existing job that requires no parameters.
The record
- CVE
- CVE-2022-20612
- Published
- Jan 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 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 <=2.329
- Affected versionversion=unspecified <=LTS 2.319.1
What conditions does exploitation require?
What is affected?
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