Arbitrary file write via incomplete path-prefix validation
Published Jan 26, 2022 · Updated Aug 3, 2024
Path traversal in Apache Karaf 4.2.14 and earlier and 4.3.0 through 4.3.5 allows attackers to write files outside an intended directory. FileUtil.unjar and the karaf-maven-plugin RunMojo compare canonical child paths with an unterminated parent-path prefix, so sibling paths sharing that prefix pass validation. Exploitation requires a user-controlled archive entry reaching an obr:* command or the Maven run goal; the resulting write is limited by the Karaf or build process account.
Summary
What happened
Path traversal in Apache Karaf 4.2.14 and earlier and 4.3.0 through 4.3.5 allows attackers to write files outside an intended directory. FileUtil.unjar and the karaf-maven-plugin RunMojo compare canonical child paths with an unterminated parent-path prefix, so sibling paths sharing that prefix pass validation. Exploitation requires a user-controlled archive entry reaching an obr:* command or the Maven run goal; the resulting write is limited by the Karaf or build process account.
The record
- CVE
- CVE-2022-22932
- Published
- Jan 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Karaf
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 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=Apache Karaf <4.2.15 changes=[{"at":"4.3.6","status":"unaffected"}]
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