Authenticated controller-file rendering via unrestricted history path
Published Sep 6, 2023 · Updated Sep 26, 2024
Path traversal in Jenkins Job Configuration History 1227.v7a_79fc4dc01f and earlier allows remote authenticated users to render unintended files. The history-entry view uses the unrestricted name query parameter as a file path, allowing traversal outside the plugin-managed history location. Exploitation requires low-privileged Jenkins access; stored script execution further requires an attacker-created controller file and a victim viewing the crafted entry.
Summary
What happened
Path traversal in Jenkins Job Configuration History 1227.v7a_79fc4dc01f and earlier allows remote authenticated users to render unintended files. The history-entry view uses the unrestricted name query parameter as a file path, allowing traversal outside the plugin-managed history location. Exploitation requires low-privileged Jenkins access; stored script execution further requires an attacker-created controller file and a victim viewing the crafted entry.
The record
- CVE
- CVE-2023-41930
- Published
- Sep 6, 2023
- Updated
- Sep 26, 2024
- Vendor
- Jenkins Project
- Product
- Job Configuration History
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- authenticated
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 <=1227.v7a_79fc4dc01f
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