File-existence disclosure via uncontained form path
Published Jul 27, 2022 · Updated Aug 3, 2024
Path traversal in Jenkins Deployer Framework Plugin 85.v1d1888e8c021 and earlier allows remote authenticated users to test file existence. StaticSelectionDeploySource.doCheckFilePath joins the submitted value to the last successful build's artifacts directory and calls File.isFile without first containing the canonical path. Item/Read permission and a job with a successful build are required; the oracle reveals existence only, not file contents.
Summary
What happened
Path traversal in Jenkins Deployer Framework Plugin 85.v1d1888e8c021 and earlier allows remote authenticated users to test file existence. StaticSelectionDeploySource.doCheckFilePath joins the submitted value to the last successful build's artifacts directory and calls File.isFile without first containing the canonical path. Item/Read permission and a job with a successful build are required; the oracle reveals existence only, not file contents.
The record
- CVE
- CVE-2022-36890
- Published
- Jul 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Deployer Framework
- Classifications
- CWE-22, T1083
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 27, 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 <=85.v1d1888e8c021
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