Arbitrary file write via unsanitized parameter path
Published Jun 22, 2022 · Updated Aug 3, 2024
Path traversal in Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier allows remote attackers to write arbitrary files. Jenkins archives an uploaded file as build metadata and treats the unsanitized file-parameter name as a relative path within a build directory. Attackers must be able to configure a Pipeline and supply file content; exploitation creates or replaces controller files with attacker-specified content.
Summary
What happened
Path traversal in Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier allows remote attackers to write arbitrary files. Jenkins archives an uploaded file as build metadata and treats the unsanitized file-parameter name as a relative path within a build directory. Attackers must be able to configure a Pipeline and supply file content; exploitation creates or replaces controller files with attacker-specified content.
The record
- CVE
- CVE-2022-34177
- Published
- Jun 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline: Input Step Plugin
- Classifications
- CWE-22, T1105
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 22, 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 <=448.v37cea_9a_10a_70
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