Loading vulnerability…
CVE-2024-28863 is an uncontrolled resource-consumption vulnerability in node-tar versions earlier than 6.2.1. The archive extraction folder-creation process does not enforce a limit on nested directory depth. A crafted tar archive containing an entry with an excessively deep path causes node-tar to create or process an unbounded number of subdirectories, consuming substantial memory and potentially CPU resources.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A node-tar denial-of-service flaw when parsing tar files because folder depth is not adequately validated.
A denial-of-service vulnerability in node-tar caused by insufficient folder-depth validation while parsing tar files.
A node-tar denial-of-service vulnerability caused by missing directory-depth validation while parsing TAR archives.
A denial-of-service vulnerability in node-tar before version 6.2.1. A crafted tar archive containing an excessively deep path can trigger unbounded subfolder creation, consuming memory and potentially crashing the Node.js client.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.