Disabled-module deletion via GET-accepting endpoint
Published Sep 6, 2023 · Updated Sep 26, 2024
CSRF in Jenkins Ivy Plugin 2.5 and earlier allows remote attackers to delete disabled modules through a crafted request. An Ivy Plugin HTTP endpoint performs the deletion without requiring POST, so a cross-origin GET request reaches the state-changing operation. A victim with an active Jenkins session must interact with attacker-controlled content; the consequence is limited to deletion of disabled modules.
Summary
What happened
CSRF in Jenkins Ivy Plugin 2.5 and earlier allows remote attackers to delete disabled modules through a crafted request. An Ivy Plugin HTTP endpoint performs the deletion without requiring POST, so a cross-origin GET request reaches the state-changing operation. A victim with an active Jenkins session must interact with attacker-controlled content; the consequence is limited to deletion of disabled modules.
The record
- CVE
- CVE-2023-41938
- Published
- Sep 6, 2023
- Updated
- Sep 26, 2024
- Vendor
- Jenkins Project
- Product
- Ivy Plugin
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 6, 2023CVE publishedPublication date reported by the CVE source.
- Sep 26, 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.5
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