Security readout for executives and security teams
Plain-English summary
This flaw could cause npm workspace projects to publish files that maintainers meant to exclude. The main business risk is accidental exposure of private code, configuration, credentials, or internal metadata in public or private npm packages. It is a supply-chain confidentiality issue, not a remote code execution vulnerability.
Executive priority
Treat this as a high-priority exposure review for teams publishing npm workspace packages. The urgent task is not exploit blocking, but confirming whether sensitive files were already released and containing any disclosure.
Technical view
When npm pack or publish ran in a workspace, npm ignored root-level .gitignore and .npmignore exclusion rules. The issue affected workspace packing from npm v7.9.0 and workspace publishing from v7.13.0, with the patched npm v8.11.0 included in specified Node.js releases.
Likely exposure
Most exposure is in organizations publishing npm packages from monorepos or npm workspaces using affected npm versions. The highest-risk cases are public packages or internal registries where sensitive files were excluded only by root-level ignore files.
Exploitation context
The source bundle does not show known active exploitation, and KEV status is false. Exploitation would primarily mean accessing already-published package contents that unintentionally included sensitive files. No source indicates integrity or availability impact.
Researcher notes
Focus on npm workspace publication paths, package tarball contents, and root-level ignore reliance. Evidence supports confidentiality impact through unintended file inclusion. The bundle names patched npm v8.11.0 and Node.js v16.15.1, v17.9.1, and v18.3.0 as including the fix.
Mitigation direction
- Upgrade npm to v8.11.0 or later.
- Use Node.js releases that bundle patched npm v8.11.0 or later.
- Audit packages published from affected workspaces for unintended files.
- Remove or replace exposed package versions where feasible.
- Rotate credentials or secrets if published package contents exposed them.
- Check vendor guidance for any ecosystem-specific remediation details.
Validation and detection
- Inventory npm workspaces that used npm v7.9.0 through pre-v8.11.0 tooling.
- Identify packages published from workspaces since the affected npm versions were introduced.
- Compare published package contents against intended root .gitignore and .npmignore exclusions.
- Confirm current build and release runners use patched npm.
- Review registry artifacts for secrets, private source, configs, or internal metadata.
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-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCVE-2022-29244 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
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/npm/cli/security/advisories/GHSA-hj9c-8jmm-8c52CVE reference · x_refsource_MISC
- https://github.com/npm/npm-packlistCVE reference · x_refsource_MISC
- https://github.com/npm/cli/tree/latest/workspaces/libnpmpublishCVE reference · x_refsource_MISC
- https://github.com/npm/cli/tree/latest/workspaces/libnpmpackCVE reference · x_refsource_MISC
- https://github.com/nodejs/node/pull/43210CVE reference · x_refsource_MISC
- https://github.com/npm/cli/releases/tag/v8.11.0CVE reference · x_refsource_MISC
- https://github.com/nodejs/node/releases/tag/v16.15.1CVE reference · x_refsource_MISC
- https://github.com/nodejs/node/releases/tag/v17.9.1CVE reference · x_refsource_MISC
- https://github.com/nodejs/node/releases/tag/v18.3.0CVE reference · x_refsource_MISC
- https://security.netapp.com/advisory/ntap-20220722-0007/CVE 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.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.