Build-log deletion via unchecked HTTP handler
Published Nov 15, 2022 · Updated Apr 30, 2025
Missing authorization in Jenkins Delete log Plugin 1.0 and earlier allows remote authenticated users to delete build logs over HTTP. The LogDelete.doDelete handler accepts Submit=Yes and calls delete() on build and matrix-run log files without checking Item permissions. Item/Read access is sufficient, and exploitation permanently removes build-output records without altering jobs or executing code.
Summary
What happened
Missing authorization in Jenkins Delete log Plugin 1.0 and earlier allows remote authenticated users to delete build logs over HTTP. The LogDelete.doDelete handler accepts Submit=Yes and calls delete() on build and matrix-run log files without checking Item permissions. Item/Read access is sufficient, and exploitation permanently removes build-output records without altering jobs or executing code.
The record
- CVE
- CVE-2022-45394
- Published
- Nov 15, 2022
- Updated
- Apr 30, 2025
- Vendor
- Jenkins Project
- Product
- Delete log
- Classifications
- CWE-862, T1485
- 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.
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