Arbitrary file write via misvalidated tar paths
Published Jan 8, 2025 · Updated Jan 9, 2025
Path traversal in Keras 3.7.0 allows attackers to write files outside the extraction directory through a crafted tar archive. The get_file path invokes extract_archive, whose filter_safe_paths validates tar member names against the process working directory instead of the requested extraction directory before extractall writes them. Exploitation requires a user or user-run process to download and extract the attacker-controlled archive, and resulting writes carry the Keras process's permissions.
Summary
What happened
Path traversal in Keras 3.7.0 allows attackers to write files outside the extraction directory through a crafted tar archive. The get_file path invokes extract_archive, whose filter_safe_paths validates tar member names against the process working directory instead of the requested extraction directory before extractall writes them. Exploitation requires a user or user-run process to download and extract the attacker-controlled archive, and resulting writes carry the Keras process's permissions.
The record
- CVE
- CVE-2024-55459
- Published
- Jan 8, 2025
- Updated
- Jan 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, CWE-494, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2025CVE publishedPublication date reported by the CVE source.
- Jan 9, 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.
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
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