Security readout for executives and security teams
Plain-English summary
CVE-2021-32803 affects the npm tar package, also known as node-tar. A malicious tar archive could cause files to be created or overwritten outside the intended extraction location. Business risk is highest where systems automatically unpack archives from users, partners, package workflows, or build pipelines.
Executive priority
Treat as a high-priority dependency remediation if archive extraction is exposed to untrusted inputs or automated supply-chain workflows. If node-tar is only present in isolated tooling with trusted inputs, urgency is lower but upgrade should still be scheduled.
Technical view
Vulnerable node-tar versions cached created directories and skipped later symlink checks for cached paths. An archive could exploit this cache behavior to bypass symlink protections and write files to unintended locations. Fixed releases are 3.2.3, 4.4.15, 5.0.7, and 6.1.2.
Likely exposure
Exposure is likely in Node.js applications, developer tools, CI systems, or products that depend on vulnerable node-tar versions and extract untrusted tar archives. Transitive dependency exposure should be considered. Oracle and Siemens advisories indicate downstream product relevance, but this bundle does not define specific affected product versions beyond node-tar.
Exploitation context
The CVSS vector requires local attack conditions and user interaction, but no privileges. The provided bundle does not show CISA KEV listing or confirmed active exploitation. Practical risk depends on whether vulnerable software processes attacker-controlled tar archives.
Researcher notes
The core issue is directory cache poisoning that weakens symlink defense during extraction. CVSS 8.2 reflects changed scope with high confidentiality and integrity impact, but no availability impact. Evidence in this bundle supports fixed versions, not exploit-in-the-wild claims.
Mitigation direction
- Upgrade npm tar to a fixed version or later.
- Audit direct and transitive dependencies for vulnerable node-tar ranges.
- Avoid extracting untrusted tar archives until vulnerable dependencies are remediated.
- Review vendor advisories for packaged products that embed node-tar.
- Refresh lockfiles and redeploy affected build or runtime environments.
Validation and detection
- Check SBOMs and lockfiles for npm tar versions below fixed releases.
- Confirm deployed artifacts include fixed node-tar versions.
- Identify application paths that extract user, partner, or CI-supplied tar archives.
- Run dependency scanning mapped to CVE-2021-32803.
- Review vendor bulletins for Oracle or Siemens product exposure where applicable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-32803 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N1.85.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhwCVE reference · x_refsource_CONFIRM
- https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20CVE reference · x_refsource_MISC
- https://www.npmjs.com/advisories/1771CVE reference · x_refsource_MISC
- https://www.npmjs.com/package/tarCVE reference · x_refsource_MISC
- https://www.oracle.com/security-alerts/cpuoct2021.htmlCVE reference · x_refsource_MISC
- https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdfCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
