Node.js client crash via unbounded path depth
Published Mar 21, 2024 · Updated Feb 13, 2025
Denial of service in node-tar before 6.2.1 allows remote attackers to crash a Node.js client through a deeply nested tar archive. The Unpack CHECKPATH path accepted archive-entry paths of unbounded depth, so extraction recursively created folders until CPU and heap resources were exhausted. A user or application must extract the attacker-supplied archive; reported effects are resource exhaustion and process crash, not data access or modification.
Summary
What happened
Denial of service in node-tar before 6.2.1 allows remote attackers to crash a Node.js client through a deeply nested tar archive. The Unpack CHECKPATH path accepted archive-entry paths of unbounded depth, so extraction recursively created folders until CPU and heap resources were exhausted. A user or application must extract the attacker-supplied archive; reported effects are resource exhaustion and process crash, not data access or modification.
The record
- CVE
- CVE-2024-28863
- Published
- Mar 21, 2024
- Updated
- Feb 13, 2025
- Vendor
- Node-tar Project
- Product
- node-tar
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 21, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.2.1
What conditions does exploitation require?
What is affected?
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
- Deeply nested tar archive 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