# CVE-2023-33290: git-url-parse crate vulnerable to Regular Expression Denial of Service

> Attackers can cause denial of service in applications using the git-url-parse Rust crate by submitting crafted URLs that trigger excessive regex processing.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2023
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-qfh9-8p57-mjjj

## What is CVE-2023-33290?

CVE-2023-33290 is a high-severity denial of service vulnerability in n/a, published on 12 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The git-url-parse crate through 0.4.4 for Rust allows Regular Expression Denial of Service (ReDos) via a crafted URL to normalize_url in lib.rs, a similar issue to CVE-2023-32758 (Python).

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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

2 open source packages ship an affected version, including git-url-parse. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `git-url-parse` | crates.io | All versions to 0.4.4 | None |
| `git-url-parse` | crates.io | All versions to 0.4.4 | None |

Products: Git-Url-Parse Project Git-Url-Parse.

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

No fix has been published for CVE-2023-33290 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-33290 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33290 is a high-severity denial of service vulnerability in n/a, published on 12 Jun 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-33290 in the wild and no public exploit code.

Affected packages and fixed versions:
- git-url-parse (crates.io): affected all versions up to 0.4.4; no fix listed
- git-url-parse (crates.io): affected all versions up to 0.4.4; no fix listed

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

## Sources

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

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