# GHSA-gf8q-jrpm-jvxq: URL parsing in node-forge could lead to undesired behavior.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Jan 2022

## What is GHSA-gf8q-jrpm-jvxq?

GHSA-gf8q-jrpm-jvxq is a vulnerability in node-forge, published on 8 Jan 2022. 

### Official description

### Impact
The regex used for the `forge.util.parseUrl` API would not properly parse certain inputs resulting in a parsed data structure that could lead to undesired behavior.

### Patches
`forge.util.parseUrl` and other very old related URL APIs were removed in 1.0.0 in favor of letting applications use the more modern WHATWG URL Standard API.

### Workarounds
Ensure code does not directly or indirectly call `forge.util.parseUrl` with untrusted input.

### References
- https://www.huntr.dev/bounties/41852c50-3c6d-4703-8c55-4db27164a4ae/

### 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-gf8q-jrpm-jvxq?

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


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

## How do I fix GHSA-gf8q-jrpm-jvxq?

Upgrade node-forge to 1.0.0 or later.

## Is GHSA-gf8q-jrpm-jvxq being exploited?

There is no known exploitation of GHSA-gf8q-jrpm-jvxq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-gf8q-jrpm-jvxq and fix it if it is affected.

What it is: GHSA-gf8q-jrpm-jvxq is a vulnerability in node-forge, published on 8 Jan 2022. 
Exploitation: There is no known exploitation of GHSA-gf8q-jrpm-jvxq in the wild and no public exploit code.

Affected packages and fixed versions:
- node-forge (npm): affected all versions; fixed in 1.0.0
- node-forge (npm): affected all versions; fixed in 1.0.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-gf8q-jrpm-jvxq/ (Markdown: https://insights.sbomify.com/GHSA-gf8q-jrpm-jvxq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-gf8q-jrpm-jvxq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-gf8q-jrpm-jvxq/
Summaries are generated and may contain mistakes; the official description above is the record.