Node.js up to 16.15.0/17.19.0/18.2.x npm information disclosure

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Node.js up to 16.15.0/17.19.0/18.2.x. The affected element is an unknown function of the component npm. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2022-29244. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Node.js up to 16.15.0/17.19.0/18.2.x (JavaScript Library) and classified as problematic. This issue affects an unknown functionality of the component npm. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

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.

The weakness was presented 06/13/2022 as GHSA-hj9c-8jmm-8c52. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-29244 since 04/13/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 216256 (Oracle Linux 8 : nodejs:20 (ELSA-2025-1351)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 16.15.1, 17.19.1 or 18.3.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (216256). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• JavaScript Library

Name

• Node.js

Version

• 16.0
• 16.1
• 16.2
• 16.3
• 16.4
• 16.5
• 16.6
• 16.7
• 16.8
• 16.9
• 16.10
• 16.11
• 16.12
• 16.13
• 16.14
• 16.15.0
• 17.0
• 17.1
• 17.2
• 17.3
• 17.4
• 17.5
• 17.6
• 17.7
• 17.8
• 17.9
• 17.10
• 17.11
• 17.12
• 17.13
• 17.14
• 17.15
• 17.16
• 17.17
• 17.18
• 17.19.0
• 18.0
• 18.1
• 18.2

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion