Advisory

GHSA-f5x3-32g6-xq36

Also known as: CVE-2024-28863

Summary

Denial of service while parsing a tar file due to lack of folders count validation

Details

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-tar to extract it, you should get the same behavior as the video

Proof Of Concept:
Here's a video show-casing the exploit:

Impact

Denial of service by crashing the nodejs client when attempting to parse a tar archive, make it run out of heap memory and consuming server CPU and memory resources

Report resources
payload.txt
archeive.tar.gz

Note
This report was originally reported to GitHub bug bounty program, they asked me to report it to you a month ago

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-03-22 16:57 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

node-tar

npm · All systems

Affected

  • introduced 0, fixed 6.2.1 (semver)

Fixed versions

6.2.1

Fix

tar

npm · All systems

Affected

  • introduced 0, fixed 6.2.1 (semver)

Fixed versions

6.2.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences