# CVE-2022-32223: Other in Node

> An attacker can execute arbitrary code on Windows systems by placing a malicious DLL in the user directory when specific OpenSSL configurations are present.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Jul 2022
- **Updated:** 30 Apr 2025
- **Also known as:** BIT-node-2022-32223, BIT-node-min-2022-32223, GHSA-fxjx-rf8x-pxw8

## What is CVE-2022-32223?

CVE-2022-32223 is a high-severity vulnerability in Nodejs Node.js, published on 14 Jul 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Node.js is vulnerable to Hijack Execution Flow: DLL Hijacking under certain conditions on Windows platforms.This vulnerability can be exploited if the victim has the following dependencies on a Windows machine:* OpenSSL has been installed and “C:\Program Files\Common Files\SSL\openssl.cnf” exists.Whenever the above conditions are present, `node.exe` will search for `providers.dll` in the current user directory.After that, `node.exe` will try to search for `providers.dll` by the DLL Search Order in Windows.It is possible for an attacker to place the malicious file `providers.dll` under a variety of paths and exploit this vulnerability.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2022-32223?

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 14.0.0 | 14.14.1, 14.20.0, 16.12.1, 16.16.0, 18.0.5 |
| `node-min` | Bitnami | From 14.0.0 | 14.14.1, 14.20.0, 16.12.1, 16.16.0, 18.0.5 |

Products: Nodejs Node.js.

## How do I fix CVE-2022-32223?

Upgrade node to a fixed version for your release line: 14.14.1, 14.20.0, 16.12.1 or 16.16.0.

## Is CVE-2022-32223 being exploited?

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

Public exploit code:

- https://github.com/ianyong/cve-2022-32223 (github_poc): https://github.com/ianyong/cve-2022-32223

## 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-2022-32223 and fix it if it is affected.

What it is: CVE-2022-32223 is a high-severity vulnerability in Nodejs Node.js, published on 14 Jul 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-32223 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected from 14.0.0; fixed in 14.14.1, 14.20.0, 16.12.1, 16.16.0, 18.0.5
- node-min (Bitnami): affected from 14.0.0; fixed in 14.14.1, 14.20.0, 16.12.1, 16.16.0, 18.0.5

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-2022-32223/ (Markdown: https://insights.sbomify.com/CVE-2022-32223/index.md)
```

## Sources

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

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