cve.bz

CVE-2023-30585 nodejs node.js

7.5 highEPSS 1.5%

High (7.5) in nodejs node.js. EPSS 1.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
1.5% (unchanged from 1.5% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 74th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-30585 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-30585?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-30585?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-30585 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2023-30585

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2023-30585](https://cve.bz/cve/badge/CVE-2023-30585.svg)](https://cve.bz/cve/CVE-2023-30585)

HTML:

<a href="https://cve.bz/cve/CVE-2023-30585"><img src="https://cve.bz/cve/badge/CVE-2023-30585.svg" alt="CVE-2023-30585"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
NodeJS Nodefrom 4.0 before 4.*
NodeJS Nodefrom 5.0 before 5.*
NodeJS Nodefrom 6.0 before 6.*
NodeJS Nodefrom 7.0 before 7.*
NodeJS Nodefrom 8.0 before 8.*
NodeJS Nodefrom 9.0 before 9.*
NodeJS Nodefrom 10.0 before 10.*
NodeJS Nodefrom 11.0 before 11.*
NodeJS Nodefrom 12.0 before 12.*
NodeJS Nodefrom 13.0 before 13.*
NodeJS Nodefrom 14.0 before 14.*
NodeJS Nodefrom 15.0 before 15.*
NodeJS Nodefrom 16.0 before 16.20.1
NodeJS Nodefrom 17.0 before 17.*
NodeJS Nodefrom 18.0 before 18.16.1
NodeJS Nodefrom 19.0 before 19.*
NodeJS Nodefrom 20.0 before 20.3.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-ESPOS, Linux Enterprise High Performance Computing 15 SP3-LTSS and 3 morenodejs1616.20.1-150300.7.24.2SUSE-SU-2023:2861-1
SUSELinux Enterprise Module for Web and Scripting 12nodejs1616.20.1-8.30.1SUSE-SU-2023:2655-1
SUSELinux Enterprise Module for Web and Scripting 12nodejs1818.16.1-8.9.1SUSE-SU-2023:2662-1
SUSELinux Enterprise Module for Web and Scripting 15 SP4nodejs1616.20.1-150400.3.21.1SUSE-SU-2023:2663-1
SUSELinux Enterprise Module for Web and Scripting 15 SP4, Linux Enterprise Module for Web and Scripting 15 SP5nodejs1818.16.1-150400.9.9.1SUSE-SU-2023:2669-1
openSUSELeap 15.4nodejs1616.20.1-150400.3.21.1SUSE-SU-2023:2663-1
openSUSELeap 15.4, Leap 15.5nodejs1818.16.1-150400.9.9.1SUSE-SU-2023:2669-1
openSUSETumbleweednodejs2020.3.1-1.1openSUSE-SU-2024:13021-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This CVE only affects the Windows version of NodeJS.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8nodejs:14/nodejsNot affected
Red Hat Enterprise Linux 8nodejs:16/nodejsNot affected
Red Hat Enterprise Linux 8nodejs:18/nodejsNot affected
Red Hat Enterprise Linux 9nodejsNot affected
Red Hat Enterprise Linux 9nodejs:18/nodejsNot affected
Red Hat Software Collectionsrh-nodejs14-nodejsNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-30585.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-24-046-15Siemens SINEC NMS2024-02-13MultipleSINEC NMSnone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

References

Check your stackJSON