A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Nod
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.*, 5.*, 6.*, 7.*, 8.*, and 12 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the "msiexec.exe" process, running under the NT AUTHORITY\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry. The issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the "msiexec.exe" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations. The severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or "non-privileged") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged "msiexec.exe" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations. It is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- NodeJS Node
From 4.0 · fixed in 4.*; From 5.0 · fixed in 5.*; From 6.0 · fixed in 6.*; From 7.0 · fixed in 7.*; From 8.0 · fixed in 8.*; From 9.0 · fixed in 9.*; From 10.0 · fixed in 10.*; From 11.0 · fixed in 11.*; From 12.0 · fixed in 12.*; From 13.0 · fixed in 13.*; From 14.0 · fixed in 14.*; From 15.0 · fixed in 15.*; From 16.0 · fixed in 16.20.1; From 17.0 · fixed in 17.*; From 18.0 · fixed in 18.16.1; From 19.0 · fixed in 19.*; From 20.0 · fixed in 20.3.1
- nodeBitnami
From 16.0.0 · fixed in 16.20.1; From 18.0.0 · fixed in 18.16.1; From 20.0.0 · fixed in 20.3.1
- node-minBitnami
From 16.0.0 · fixed in 16.20.1; From 18.0.0 · fixed in 18.16.1; From 20.0.0 · fixed in 20.3.1