# CVE-2022-25887: Regular Expression Denial of Service (ReDoS)

> An attacker can cause a denial of service in applications using sanitize-html by exploiting insecure regular expression logic during HTML comment removal.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** CLSA-2026-1776645373, DEBIAN-CVE-2022-25887, GHSA-cgfm-xwp7-2cvr, ROOT-APP-NPM-CVE-2022-25887, UBUNTU-CVE-2022-25887, USN-7464-1

## What is CVE-2022-25887?

CVE-2022-25887 is a medium-severity denial of service vulnerability in sanitize-html, published on 30 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The package sanitize-html before 2.7.1 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure global regular expression replacement logic of HTML comment removal.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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

2 open source packages ship an affected version, including sanitize-html. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sanitize-html` | npm | All versions | 2.7.1 |
| `sanitize-html` | npm | All versions | 2.7.1 |

Products: Apostrophecms Sanitize-Html.

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

Upgrade sanitize-html to 2.7.1 or later.

## Is CVE-2022-25887 being exploited?

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

## Other vulnerabilities in sanitize-html

- [CVE-2014-125128](https://insights.sbomify.com/CVE-2014-125128/): Cross-site scripting in apostrophecms:sanitize-html (medium 6.1)
- [CVE-2019-25225](https://insights.sbomify.com/CVE-2019-25225/): sanitize-html is vulnerable to XSS through incomprehensive sanitization (medium 6.1)
- [CVE-2016-1000237](https://insights.sbomify.com/CVE-2016-1000237/): Cross-Site Scripting in sanitize-html (medium 6.1)
- [CVE-2024-21501](https://insights.sbomify.com/CVE-2024-21501/): sanitize-html Information Exposure vulnerability (medium 5.3)
- [CVE-2021-26539](https://insights.sbomify.com/CVE-2021-26539/): Improper Input Validation in sanitize-html (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25887 and fix it if it is affected.

What it is: CVE-2022-25887 is a medium-severity denial of service vulnerability in sanitize-html, published on 30 Aug 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 CVE-2022-25887 in the wild and no public exploit code.

Affected packages and fixed versions:
- sanitize-html (npm): affected all versions; fixed in 2.7.1
- sanitize-html (npm): affected all versions; fixed in 2.7.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-2022-25887/ (Markdown: https://insights.sbomify.com/CVE-2022-25887/index.md)
```

## Sources

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

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