Build triggering via non-POST endpoint
Published Mar 6, 2024 · Updated Feb 13, 2025
Cross-site request forgery in Jenkins Subversion Partial Release Manager Plugin 1.0.1 and earlier allows remote attackers to trigger builds. An HTTP endpoint that starts a plugin-managed release build accepts non-POST requests, so a cross-origin request can invoke its state-changing action. The endpoint is exposed for jobs configured with the plugin, and successful exploitation launches a build under the Jenkins controller's existing authority.
Summary
What happened
Cross-site request forgery in Jenkins Subversion Partial Release Manager Plugin 1.0.1 and earlier allows remote attackers to trigger builds. An HTTP endpoint that starts a plugin-managed release build accepts non-POST requests, so a cross-origin request can invoke its state-changing action. The endpoint is exposed for jobs configured with the plugin, and successful exploitation launches a build under the Jenkins controller's existing authority.
The record
- CVE
- CVE-2024-28158
- Published
- Mar 6, 2024
- Updated
- Feb 13, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins Subversion Partial Release Manager Plugin
- Classifications
- CWE-352, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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 <=1.0.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