Failure Cause deletion via state-changing GET
Published Sep 20, 2023 · Updated Sep 24, 2024
Cross-site request forgery in Jenkins Build Failure Analyzer Plugin 2.4.1 and earlier allows remote attackers to delete Failure Causes. The CauseManagement.doRemoveConfirm HTTP endpoint accepts state-changing GET requests and removes the selected cause without enforcing POST. Exploitation requires a logged-in user with the plugin's RemoveCauses permission to visit attacker-controlled content; deletion alters the shared failure-cause knowledge base.
Summary
What happened
Cross-site request forgery in Jenkins Build Failure Analyzer Plugin 2.4.1 and earlier allows remote attackers to delete Failure Causes. The CauseManagement.doRemoveConfirm HTTP endpoint accepts state-changing GET requests and removes the selected cause without enforcing POST. Exploitation requires a logged-in user with the plugin's RemoveCauses permission to visit attacker-controlled content; deletion alters the shared failure-cause knowledge base.
The record
- CVE
- CVE-2023-43502
- Published
- Sep 20, 2023
- Updated
- Sep 24, 2024
- Vendor
- Jenkins Project
- Product
- Build Failure Analyzer Plugin
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=0 <=2.4.1
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