Build promotion via non-POST action endpoints
Published Apr 7, 2021 · Updated Oct 15, 2024
Cross-site request forgery in Jenkins Promoted Builds Plugin 3.9 and earlier allows remote attackers to promote builds through crafted requests. The doForcePromotion, Status.doBuild, and ManualCondition.doApprove web methods lacked POST-only annotations and accepted state-changing requests. Exploitation requires an authenticated victim to follow an attacker-controlled request and can trigger regular, forced, or re-executed build promotions.
Summary
What happened
Cross-site request forgery in Jenkins Promoted Builds Plugin 3.9 and earlier allows remote attackers to promote builds through crafted requests. The doForcePromotion, Status.doBuild, and ManualCondition.doApprove web methods lacked POST-only annotations and accepted state-changing requests. Exploitation requires an authenticated victim to follow an attacker-controlled request and can trigger regular, forced, or re-executed build promotions.
The record
- CVE
- CVE-2021-21641
- Published
- Apr 7, 2021
- Updated
- Oct 15, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins Promoted Builds Plugin
- Classifications
- CWE-352, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2021CVE publishedPublication date reported by the CVE source.
- Oct 15, 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 <=3.9
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.
Weakness, pattern, technique
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