# GHSA-wxgw-qj99-44c2: Prototype Pollution in node-forge util.setPath API

> Prototype pollution in node-forge allows attackers to manipulate object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jan 2022

## What is GHSA-wxgw-qj99-44c2?

GHSA-wxgw-qj99-44c2 is a vulnerability in node-forge, published on 8 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact
`forge.util.setPath` had a potential prototype pollution issue if called with untrusted keys. This API was not used by forge itself.

### Patches
The `forge.util.setPath` API and related functions were removed in 0.10.0.

### Workarounds
Don't call `forge.util.setPath` directly or indirectly with untrusted keys.

### References
- https://security.snyk.io/vuln/SNYK-JS-NODEFORGE-598677
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7720

### For more information
If you have any questions or comments about this advisory:
* Open an issue in [forge](https://github.com/digitalbazaar/forge).
* Email us at support@digitalbazaar.com.

## Which versions are affected by GHSA-wxgw-qj99-44c2?

2 open source packages ship an affected version, including node-forge.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-forge` | npm | All versions | 0.10.0 |
| `node-forge` | npm | All versions | 0.10.0 |

## How do I fix GHSA-wxgw-qj99-44c2?

Upgrade node-forge to 0.10.0 or later.

## Is GHSA-wxgw-qj99-44c2 being exploited?

There is no known exploitation of GHSA-wxgw-qj99-44c2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wxgw-qj99-44c2 and fix it if it is affected.

What it is: GHSA-wxgw-qj99-44c2 is a vulnerability in node-forge, published on 8 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-wxgw-qj99-44c2 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-forge (npm): affected all versions; fixed in 0.10.0
- node-forge (npm): affected all versions; fixed in 0.10.0

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/GHSA-wxgw-qj99-44c2/ (Markdown: https://insights.sbomify.com/GHSA-wxgw-qj99-44c2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wxgw-qj99-44c2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wxgw-qj99-44c2/
Summaries are generated and may contain mistakes; the official description above is the record.