Application crash via stack-allocated PAX attributes
Published Mar 27, 2024 · Updated Nov 4, 2025
Stack overflow in GNU tar before 1.35 allows local users to crash the application by extracting a crafted PAX archive. The xattr_decoder function allocates attacker-controlled extended-attribute keys and values on the stack, exhausting stack space as crafted attribute sizes grow. The user must cause an affected tar process to parse the archive; the demonstrated consequence is process termination without data disclosure or modification.
Summary
What happened
Stack overflow in GNU tar before 1.35 allows local users to crash the application by extracting a crafted PAX archive. The xattr_decoder function allocates attacker-controlled extended-attribute keys and values on the stack, exhausting stack space as crafted attribute sizes grow. The user must cause an affected tar process to parse the archive; the demonstrated consequence is process termination without data disclosure or modification.
The record
- CVE
- CVE-2023-39804
- Published
- Mar 27, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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