Arbitrary file read via unrestricted input folder
Published Mar 29, 2022 · Updated Aug 3, 2024
Path traversal in Jenkins Continuous Integration with Toad Edge Plugin 2.3 and earlier allows remote authenticated users to read controller files. Affected build steps accept an input-folder parameter that can name a directory on the Jenkins controller, then copy files from that controller path instead of constraining access to the executing agent's workspace. Item/Configure permission is required, and disclosure is limited to files readable by the Jenkins controller process.
Summary
What happened
Path traversal in Jenkins Continuous Integration with Toad Edge Plugin 2.3 and earlier allows remote authenticated users to read controller files. Affected build steps accept an input-folder parameter that can name a directory on the Jenkins controller, then copy files from that controller path instead of constraining access to the executing agent's workspace. Item/Configure permission is required, and disclosure is limited to files readable by the Jenkins controller process.
The record
- CVE
- CVE-2022-28146
- Published
- Mar 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Continuous Integration with Toad Edge
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 29, 2022CVE 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 <=2.3
What conditions does exploitation require?
What is affected?
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