CVE-2024-28863
published 2024-03-21CVE-2024-28863: node-tar is a Tar for Node.js. node-tar prior to version 6.2.1 has no limit on the number of sub-folders created in the folder creation process. An attacker…
PriorityP430medium6.5CVSS 3.1
AVNACLPRNUIRSUCNINAH
EPSS
0.93%
56.1th percentile
node-tar is a Tar for Node.js. node-tar prior to version 6.2.1 has no limit on the number of sub-folders created in the folder creation process. An attacker who generates a large number of sub-folders can consume memory on the system running node-tar and even crash the Node.js client within few seconds of running it using a path with too many sub-folders inside. Version 6.2.1 fixes this issue by preventing extraction in excessively deep sub-folders.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | node-tar | < node-tar 6.1.13+~cs7.0.5-2 (forky) | node-tar 6.1.13+~cs7.0.5-2 (forky) |
| gnu | tar | >= 0 < 6.2.1 | 6.2.1 |
| isaacs | node-tar | < 6.2.1 | 6.2.1 |
| isaacs | node-tar | >= 0 < 6.1.13+~cs7.0.5-2 | 6.1.13+~cs7.0.5-2 |
| isaacs | node-tar | >= 0 < 6.1.13+~cs7.0.5-2 | 6.1.13+~cs7.0.5-2 |
| isaacs | node-tar | >= 0 < 6.2.1 | 6.2.1 |
| isaacs | tar | < 6.2.1 | 6.2.1 |
| msrc | azl3_nodejs_20.10.0-2_on_azure_linux_3.0 | — | — |
| msrc | azl3_nodejs_20.14.0-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_python-tensorboard_2.16.2-6_on_azure_linux_3.0 | — | — |
| msrc | azl3_tar_1.35-2_on_azure_linux_3.0 | — | — |
| msrc | azure_linux_3.0_arm | — | — |
| msrc | azure_linux_3.0_x64 | — | — |
| msrc | cbl2_nodejs18_18.20.2-2_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_nodejs18_18.20.3-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_python-tensorboard_2.11.0-3_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_reaper_3.1.1-17_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_reaper_3.1.1-18_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_tar_1.34-3_on_cbl_mariner_2.0 | — | — |
| msrc | cbl_mariner_2.0_arm | — | — |
| msrc | cbl_mariner_2.0_x64 | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
osv6.5MEDIUM
vendor_debian6.5MEDIUM
vendor_msrc6.5MEDIUM
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Denial of service while parsing a tar file due to lack of folders count validation
osv·2024-03-22
CVE-2024-28863 [MEDIUM] Denial of service while parsing a tar file due to lack of folders count validation
Denial of service while parsing a tar file due to lack of folders count validation
## Description:
During some analysis today on npm's `node-tar` package I came across the folder creation process, Basicly if you provide node-tar with a path like this `./a/b/c/foo.txt` it would create every folder and sub-folder here a, b and c until it reaches the last folder to create `foo.txt`, In-this case I noticed that there's no validation at all on the amount of folders being created, that said we're actually able to CPU and memory consume the system running node-tar and even crash the nodejs client within few seconds of running it using a path with too many sub-folders inside
## Steps To Reproduce:
You can reproduce this issue by downloading the tar file I provided in the resources and using node
GHSA
Denial of service while parsing a tar file due to lack of folders count validation
ghsa·2024-03-22
CVE-2024-28863 [MEDIUM] CWE-400 Denial of service while parsing a tar file due to lack of folders count validation
Denial of service while parsing a tar file due to lack of folders count validation
## Description:
During some analysis today on npm's `node-tar` package I came across the folder creation process, Basicly if you provide node-tar with a path like this `./a/b/c/foo.txt` it would create every folder and sub-folder here a, b and c until it reaches the last folder to create `foo.txt`, In-this case I noticed that there's no validation at all on the amount of folders being created, that said we're actually able to CPU and memory consume the system running node-tar and even crash the nodejs client within few seconds of running it using a path with too many sub-folders inside
## Steps To Reproduce:
You can reproduce this issue by downloading the tar file I provided in the resources and using node
OSV
CVE-2024-28863: node-tar is a Tar for Node
osv·2024-03-21·CVSS 6.5
CVE-2024-28863 [MEDIUM] CVE-2024-28863: node-tar is a Tar for Node
node-tar is a Tar for Node.js. node-tar prior to version 6.2.1 has no limit on the number of sub-folders created in the folder creation process. An attacker who generates a large number of sub-folders can consume memory on the system running node-tar and even crash the Node.js client within few seconds of running it using a path with too many sub-folders inside. Version 6.2.1 fixes this issue by preventing extraction in excessively deep sub-folders.
Red Hat
node-tar: denial of service while parsing a tar file due to lack of folders depth validation
vendor_redhat·2024-03-21·CVSS 6.5
CVE-2024-28863 [MEDIUM] CWE-400 node-tar: denial of service while parsing a tar file due to lack of folders depth validation
node-tar: denial of service while parsing a tar file due to lack of folders depth validation
node-tar is a Tar for Node.js. node-tar prior to version 6.2.1 has no limit on the number of sub-folders created in the folder creation process. An attacker who generates a large number of sub-folders can consume memory on the system running node-tar and even crash the Node.js client within few seconds of running it using a path with too many sub-folders inside. Version 6.2.1 fixes this issue by preventing extraction in excessively deep sub-folders.
A flaw was found in ISAACS's node-tar, where it is vulnerable to a denial of service, caused by the lack of folder count validation. The vulnerability exists due to the application not properly controlling the consumption of internal resources while p
Microsoft
node-tar vulnerable to denial of service while parsing a tar file due to lack of folders count validation
vendor_msrc·2024-03-12·CVSS 6.5
CVE-2024-28863 [MEDIUM] CWE-400 node-tar vulnerable to denial of service while parsing a tar file due to lack of folders count validation
node-tar vulnerable to denial of service while parsing a tar file due to lack of folders count validation
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
GitHub_M: GitHub_M
Customer Action Required: Yes
Rem
Debian
CVE-2024-28863: node-tar - node-tar is a Tar for Node.js. node-tar prior to version 6.2.1 has no limit on t...
vendor_debian·2024·CVSS 6.5
CVE-2024-28863 [MEDIUM] CVE-2024-28863: node-tar - node-tar is a Tar for Node.js. node-tar prior to version 6.2.1 has no limit on t...
node-tar is a Tar for Node.js. node-tar prior to version 6.2.1 has no limit on the number of sub-folders created in the folder creation process. An attacker who generates a large number of sub-folders can consume memory on the system running node-tar and even crash the Node.js client within few seconds of running it using a path with too many sub-folders inside. Version 6.2.1 fixes this issue by preventing extraction in excessively deep sub-folders.
Scope: local
bookworm: open
bullseye: open
forky: resolved (fixed in 6.1.13+~cs7.0.5-2)
sid: resolved (fixed in 6.1.13+~cs7.0.5-2)
trixie: resolved (fixed in 6.1.13+~cs7.0.5-2)
No detection rules found.
No public exploits indexed.
https://github.com/isaacs/node-tar/commit/fe8cd57da5686f8695415414bda49206a545f7f7https://github.com/isaacs/node-tar/security/advisories/GHSA-f5x3-32g6-xq36https://security.netapp.com/advisory/ntap-20240524-0005/https://github.com/isaacs/node-tar/commit/fe8cd57da5686f8695415414bda49206a545f7f7https://github.com/isaacs/node-tar/security/advisories/GHSA-f5x3-32g6-xq36https://security.netapp.com/advisory/ntap-20240524-0005/
2024-03-21
Published