ast-cli: Path traversal in tar extraction on Linux/macOS allows writes outside the install directory
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.3.51
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The ast-cli command-line tool on Linux and macOS, when installing the Vorpal ASCA engine and SCA Resolver, can be tricked into writing files outside its intended install directory by a maliciously crafted tar archive. This could allow an attacker who controls the downloaded archive to place executable files at arbitrary locations on the system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Incomplete validation of extracted archive entry paths in ast-cli's tar extraction logic on Linux and macOS (used when installing the Vorpal ASCA real-time engine and the SCA Resolver) would allow a malicious tar archive containing absolute or traversal path entries to write files outside the install directory. Windows builds were not affected, as the Windows extractor performs this path validation. Exploitation required substituting the archive served at "download.checkmarx.com". An attacker able to compromise that server and replace the archive could write arbitrary, executable files to arbitrary filesystem paths via this path traversal. Extraction now validates that each entry's destination path resolves within the working directory and rejects absolute paths.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- github.com/checkmarx/ast-cli
fixed in 2.3.51