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

> Attackers can cause denial of service in applications using react-native-reanimated via malicious input triggering ReDoS in the color parser.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-2j79-8pqc-r7x6

## What is CVE-2022-24373?

CVE-2022-24373 is a medium-severity denial of service vulnerability in react-native-reanimated, published on 30 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The package react-native-reanimated before 3.0.0-rc.1 are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper usage of regular expression in the parser of Colors.js.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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

2 open source packages ship an affected version, including react-native-reanimated. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `react-native-reanimated` | npm | All versions | 2.10.0 |
| `react-native-reanimated` | npm | All versions | 2.10.0 |

Products: Swmansion React Native Reanimated.

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

Upgrade react-native-reanimated to 2.10.0 or later.

## Is CVE-2022-24373 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24373 is a medium-severity denial of service vulnerability in react-native-reanimated, published on 30 Sep 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-24373 in the wild and no public exploit code.

Affected packages and fixed versions:
- react-native-reanimated (npm): affected all versions; fixed in 2.10.0
- react-native-reanimated (npm): affected all versions; fixed in 2.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/CVE-2022-24373/ (Markdown: https://insights.sbomify.com/CVE-2022-24373/index.md)
```

## Sources

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

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