Project builds via GET-enabled form submission
Published Mar 30, 2021 · Updated Aug 3, 2024
Cross-site request forgery in Jenkins Build With Parameters Plugin 1.5 and earlier allows remote attackers to start builds with chosen parameters. The parambuild form's BuildWithParametersAction.doConfigSubmit handler accepts non-POST requests because it lacks a RequirePOST guard. A victim with Item/Build permission must interact with attacker-controlled content; a successful request starts the configured job with attacker-specified parameter values.
Summary
What happened
Cross-site request forgery in Jenkins Build With Parameters Plugin 1.5 and earlier allows remote attackers to start builds with chosen parameters. The parambuild form's BuildWithParametersAction.doConfigSubmit handler accepts non-POST requests because it lacks a RequirePOST guard. A victim with Item/Build permission must interact with attacker-controlled content; a successful request starts the configured job with attacker-specified parameter values.
The record
- CVE
- CVE-2021-21629
- Published
- Mar 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Build With Parameters Plugin
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 30, 2021CVE 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 <=1.5
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