Arbitrary file write via incomplete path-prefix check
Published Apr 28, 2023 · Updated Jan 31, 2025
Path traversal in Cauldron cbang before 8.1.17 allows attackers to write files outside the extraction directory via a crafted TAR archive. TarFileReader::extract accepts a canonical target path when its text merely begins with the extraction path, without requiring a directory separator. Processing an attacker-controlled archive is sufficient, and extraction can create or overwrite any file writable by the calling process.
Summary
What happened
Path traversal in Cauldron cbang before 8.1.17 allows attackers to write files outside the extraction directory via a crafted TAR archive. TarFileReader::extract accepts a canonical target path when its text merely begins with the extraction path, without requiring a directory separator. Processing an attacker-controlled archive is sufficient, and extraction can create or overwrite any file writable by the calling process.
The record
- CVE
- CVE-2023-31483
- Published
- Apr 28, 2023
- Updated
- Jan 31, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2023CVE publishedPublication date reported by the CVE source.
- Jan 31, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- poc.tar path-traversal proof of conceptproof 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