# CVE-2023-30585: Path traversal in Node

> Unprivileged users can manipulate environment variables to force the Node.js MSI installer to create arbitrary folders, potentially enabling privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Nov 2023
- **Updated:** 8 Oct 2026
- **Also known as:** BIT-node-2023-30585, BIT-node-min-2023-30585, GHSA-4r2r-cf85-vmc7

## What is CVE-2023-30585?

CVE-2023-30585 is a high-severity path traversal vulnerability in Nodejs Node.js, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2023-30585?

2 open source packages ship an affected version, including node and node-min. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | From 16.0.0 | 16.20.1, 18.16.1, 20.3.1 |
| `node-min` | Bitnami | From 16.0.0 | 16.20.1, 18.16.1, 20.3.1 |

Products: Nodejs Node.js.

## How do I fix CVE-2023-30585?

Upgrade node to a fixed version for your release line: 16.20.1, 18.16.1 or 20.3.1.

## Is CVE-2023-30585 being exploited?

There is no known exploitation of CVE-2023-30585 in the wild and no public exploit code.

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30585 and fix it if it is affected.

What it is: CVE-2023-30585 is a high-severity path traversal vulnerability in Nodejs Node.js, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-30585 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected from 16.0.0; fixed in 16.20.1, 18.16.1, 20.3.1
- node-min (Bitnami): affected from 16.0.0; fixed in 16.20.1, 18.16.1, 20.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-30585/ (Markdown: https://insights.sbomify.com/CVE-2023-30585/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-30585
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-30585
- OSV: https://osv.dev/vulnerability/CVE-2023-30585

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-30585/
Summaries are generated and may contain mistakes; the official description above is the record.