Build-log deletion via unprotected HTTP endpoint
Published Nov 15, 2022 · Updated Apr 30, 2025
Cross-site request forgery in Jenkins Delete log Plugin 1.0 and earlier allows remote attackers to delete build logs via a crafted request. The LogDelete.doDelete HTTP endpoint accepts requests without requiring POST, so another site can invoke its log-deletion action through a browser. A targeted user must have Item/Read permission and interact with attacker-controlled content; successful exploitation removes the selected build log.
Summary
What happened
Cross-site request forgery in Jenkins Delete log Plugin 1.0 and earlier allows remote attackers to delete build logs via a crafted request. The LogDelete.doDelete HTTP endpoint accepts requests without requiring POST, so another site can invoke its log-deletion action through a browser. A targeted user must have Item/Read permission and interact with attacker-controlled content; successful exploitation removes the selected build log.
The record
- CVE
- CVE-2022-45393
- Published
- Nov 15, 2022
- Updated
- Apr 30, 2025
- Vendor
- Jenkins Project
- Product
- Delete log
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 15, 2022CVE publishedPublication date reported by the CVE source.
- Apr 30, 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=unspecified <=1.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