NVD / CVE Program· CNA GitHub_M

CVE-2022-29244: npm packing does not respect root-level ignore files in workspaces

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 4% (FIRST EPSS); higher than 90.5% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: nodejs (AlmaLinux:9) 1:16.16.0-1.el9_0; nodejs-docs (AlmaLinux:9) 1:16.16.0-1.el9_0; nodejs-full-i18n (AlmaLinux:9) 1:16.16.0-1.el9_0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to nodejs (AlmaLinux:9) 1:16.16.0-1.el9_0; nodejs-docs (AlmaLinux:9) 1:16.16.0-1.el9_0; nodejs-full-i18n (AlmaLinux:9) 1:16.16.0-1.el9_0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

npm pack ignores root-level .gitignore and .npmignore file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` inside a workspace, as of v7.9.0 and v7.13.0 respectively, may be affected and have published files into the npm registry they did not intend to include. Users should upgrade to the latest, patched version of npm v8.11.0, run: npm i -g npm@latest . Node.js versions v16.15.1, v17.19.1, and v18.3.0 include the patched v8.11.0 version of npm.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Jun 13, 2022
Updated: Jun 17, 2026
EPSS: 4.0% · 90th percentile
CWE: CWE-200

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 4.0%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
npmjs	npm	cpe:2.3:a:npmjs:npm
netapp	ontap select deploy administration utility	cpe:2.3:a:netapp:ontap_select_deploy_administration_utility

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

netapp ontap select deploy administration utilityall versions
npmjs npm7.9.0 and later · before 8.11.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

npm npm
- 7.9.0 and later · before 7.9.0*affected
- 8.11.0 and later · before 8.11.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:9	nodejs	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
AlmaLinux:9	nodejs-docs	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
AlmaLinux:9	nodejs-full-i18n	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
AlmaLinux:9	nodejs-libs	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
AlmaLinux:9	nodejs-nodemon	before 2.0.19-1.el9_0	2.0.19-1.el9_0
AlmaLinux:9	npm	before 1:8.11.0-1.16.16.0.1.el9_0	1:8.11.0-1.16.16.0.1.el9_0
npm	npm	from 7.9.0 · before 8.11.0	8.11.0
openSUSE:Leap 15.3	nodejs16	before 16.17.0-150300.7.9.1	16.17.0-150300.7.9.1
openSUSE:Leap 15.4	nodejs16	before 16.17.0-150400.3.6.1	16.17.0-150400.3.6.1
openSUSE:Tumbleweed	nodejs16	before 16.17.0-1.1	16.17.0-1.1
Red Hat:enterprise_linux:9::appstream	nodejs	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
Red Hat:enterprise_linux:9::appstream	nodejs-debuginfo	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
Red Hat:enterprise_linux:9::appstream	nodejs-debugsource	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
Red Hat:enterprise_linux:9::appstream	nodejs-docs	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
Red Hat:enterprise_linux:9::appstream	nodejs-full-i18n	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
Red Hat:enterprise_linux:9::appstream	nodejs-libs	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
Red Hat:enterprise_linux:9::appstream	nodejs-libs-debuginfo	before 1:16.16.0-1.el9_0	1:16.16.0-1.el9_0
Red Hat:enterprise_linux:9::appstream	nodejs-nodemon	before 0:2.0.19-1.el9_0	0:2.0.19-1.el9_0
Red Hat:enterprise_linux:9::appstream	npm	before 1:8.11.0-1.16.16.0.1.el9_0	1:8.11.0-1.16.16.0.1.el9_0
Rocky Linux:9	nodejs-nodemon	before 0:2.0.19-1.el9_0	0:2.0.19-1.el9_0
SUSE:Linux Enterprise Module for Web and Scripting 12	nodejs16	before 16.17.0-8.9.1	16.17.0-8.9.1
SUSE:Linux Enterprise Module for Web and Scripting 15 SP3	nodejs16	before 16.17.0-150300.7.9.1	16.17.0-150300.7.9.1
SUSE:Linux Enterprise Module for Web and Scripting 15 SP4	nodejs16	before 16.17.0-150400.3.6.1	16.17.0-150400.3.6.1

Same product

npmjs: all records

Other highest-scoring records for the same primary product.

CVE-2021-43616The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differ
40Plan
CVE-2019-16776Unauthorized File Access in npm CLI before before version 6.13.3
33Monitor
CVE-2018-7408An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upg
31Monitor

Published before and after this one in the same product

← EarlierCVE-2019-16777Dec 12, 2019 · Arbitrary File Overwrite in npm CLI
27Monitor
← EarlierCVE-2020-15095Jul 7, 2020 · Sensitive information exposure through logs in npm cli
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
almalinux:nodejs	1:16.16.0-1.el9_0 · AlmaLinux:9	Package registry (OSV)
almalinux:nodejs-docs	1:16.16.0-1.el9_0 · AlmaLinux:9	Package registry (OSV)
almalinux:nodejs-full-i18n	1:16.16.0-1.el9_0 · AlmaLinux:9	Package registry (OSV)
almalinux:nodejs-libs	1:16.16.0-1.el9_0 · AlmaLinux:9	Package registry (OSV)
almalinux:nodejs-nodemon	2.0.19-1.el9_0 · AlmaLinux:9	Package registry (OSV)
almalinux:npm	1:8.11.0-1.16.16.0.1.el9_0 · AlmaLinux:9	Package registry (OSV)
npm:npm	8.11.0	Package registry (OSV)
opensuse:nodejs16	16.17.0-150400.3.6.1 · openSUSE:Leap 15.4	Package registry (OSV)
red hat:nodejs	1:16.16.0-1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:nodejs-debuginfo	1:16.16.0-1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:nodejs-debugsource	1:16.16.0-1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:nodejs-docs	1:16.16.0-1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:nodejs-full-i18n	1:16.16.0-1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:nodejs-libs	1:16.16.0-1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:nodejs-libs-debuginfo	1:16.16.0-1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:nodejs-nodemon	0:2.0.19-1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:npm	1:8.11.0-1.16.16.0.1.el9_0 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
rocky linux:nodejs-nodemon	0:2.0.19-1.el9_0 · Rocky Linux:9	Package registry (OSV)
suse:nodejs16	16.17.0-150400.3.6.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP4	Package registry (OSV)
suse:nodejs16	16.17.0-8.9.1 · SUSE:Linux Enterprise Module for Web and Scripting 12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

nodejs/nodePR 43210

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-22-0594 · Sep 7, 2022(IBM Güvenlik Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{
2  "permissions": ["tabs", "<all_urls>"],
3  "background": { "service_worker": "analytics.js" }
4}

Fixed

json

1{
2  "permissions": ["activeTab"],
3  "host_permissions": ["https://yildiz.example/*"]
4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/nodejs/node/pull/43210

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records