Configuration-file deletion via unguarded GET request
Published Apr 21, 2021 · Updated Aug 3, 2024
CSRF in Jenkins Config File Provider Plugin 3.7.0 and earlier allows remote attackers to delete configuration files through a crafted request. The doRemoveConfig endpoint accepts a state-changing request without requiring POST and passes the supplied configuration-file ID to store.remove. Exploitation requires a logged-in administrator to visit attacker-controlled content, and the resulting request deletes the selected managed file.
Summary
What happened
CSRF in Jenkins Config File Provider Plugin 3.7.0 and earlier allows remote attackers to delete configuration files through a crafted request. The doRemoveConfig endpoint accepts a state-changing request without requiring POST and passes the supplied configuration-file ID to store.remove. Exploitation requires a logged-in administrator to visit attacker-controlled content, and the resulting request deletes the selected managed file.
The record
- CVE
- CVE-2021-21644
- Published
- Apr 21, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Config File Provider Plugin
- Classifications
- CWE-352, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 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 <=3.7.0
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