Authenticated file read via path traversal
Published Jun 14, 2023 · Updated Dec 31, 2024
Path traversal in Jenkins Project AWS CodeCommit Trigger 3.0.12 and earlier allows remote authenticated users to read controller files. SQSActivityAction.doDownload appends the unvalidated request path to activityDir and serves the resulting file, so ../ sequences escape the log directory. Item/Read permission and a job configured with the SQS build trigger are required; exposed controller files can include stored Jenkins credentials.
Summary
What happened
Path traversal in Jenkins Project AWS CodeCommit Trigger 3.0.12 and earlier allows remote authenticated users to read controller files. SQSActivityAction.doDownload appends the unvalidated request path to activityDir and serves the resulting file, so ../ sequences escape the log directory. Item/Read permission and a job configured with the SQS build trigger are required; exposed controller files can include stored Jenkins credentials.
The record
- CVE
- CVE-2023-35147
- Published
- Jun 14, 2023
- Updated
- Dec 31, 2024
- Vendor
- Jenkins Project
- Product
- AWS CodeCommit Trigger
- Classifications
- CWE-732, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 14, 2023CVE publishedPublication date reported by the CVE source.
- Dec 31, 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 <=3.0.12
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
- GitHub Security Lab path-traversal request examplesproof of concept · demonstrated
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