CVE-2022-24373 is a medium-severity (CVSS 5.3) CWE-1333 vulnerability in react-native-reanimated. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for react-native-reanimated — see the affected versions and patch details below.
Regular Expression Denial of Service (ReDoS)
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-24373.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
react-native-reanimatednpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-native-reanimated | all versions | 2.10.0npm install react-native-reanimated@2.10.0 |
Affected Products
react native reanimatedswmansionResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-native-reanimated, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update react-native-reanimated to 2.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24373 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2022-24373 in your dependencies?
Find it across npm, including transitive dependencies.