# CVE-2021-3795: Inefficient Regular Expression Complexity in sindresorhus/semver-regex

> Attackers can cause denial of service in applications using semver-regex by triggering inefficient regular expression complexity.

- **Severity:** High 7.5 (`CVSS:3.0/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:** Yes
- **Published:** 15 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-44c6-4v22-4mhx, ROOT-APP-NPM-CVE-2021-3795

## What is CVE-2021-3795?

CVE-2021-3795 is a high-severity denial of service vulnerability in sindresorhus/semver-regex, published on 15 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

semver-regex is vulnerable to Inefficient Regular Expression Complexity

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2021-3795?

4 open source packages ship an affected version, including semver-regex. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `semver-regex` | npm | All versions | 3.1.3 |
| `semver-regex` | npm | All versions | 3.1.3 |
| `semver-regex` | npm | From 4.0.0 | 4.0.1 |
| `semver-regex` | npm | From 4.0.0 | 4.0.1 |

Products: Semver-Regex Project Semver-Regex.

## How do I fix CVE-2021-3795?

Upgrade semver-regex to a fixed version for your release line: 3.1.3 or 4.0.1.

## Is CVE-2021-3795 being exploited?

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

## Other vulnerabilities in sindresorhus/semver-regex

- [CVE-2021-43307](https://insights.sbomify.com/CVE-2021-43307/): Exponential ReDoS in semver-regex (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3795 and fix it if it is affected.

What it is: CVE-2021-3795 is a high-severity denial of service vulnerability in sindresorhus/semver-regex, published on 15 Sep 2021. 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-2021-3795 in the wild and no public exploit code.

Affected packages and fixed versions:
- semver-regex (npm): affected all versions; fixed in 3.1.3
- semver-regex (npm): affected all versions; fixed in 3.1.3
- semver-regex (npm): affected from 4.0.0; fixed in 4.0.1
- semver-regex (npm): affected from 4.0.0; fixed in 4.0.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-2021-3795/ (Markdown: https://insights.sbomify.com/CVE-2021-3795/index.md)
```

## Sources

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

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