CVE-2024-45813 is a medium-severity (CVSS 5.3) CWE-1333 vulnerability in find-my-way. A fix is available for find-my-way — see the affected versions and patch details below.
ReDoS vulnerability in multiparametric routes in find-my-way
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-2024-45813.
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.
find-my-waynpmDescription
find-my-way is a fast, open source HTTP router, internally using a Radix Tree (aka compact Prefix Tree), supports route params, wildcards, and it's framework independent. A bad regular expression is generated any time one has two parameters within a single segment, when adding a - at the end, like /:a-:b-. This may cause a denial of service in some instances. Users are advised to update to find-my-way v8.2.2 or v9.0.1. or subsequent versions. There are no known workarounds for this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | find-my-way | ≥ 5.5.0&&< 8.2.2 | 8.2.2npm install find-my-way@8.2.2 |
| 📦npm | find-my-way | ≥ 9.0.0&&< 9.0.1 | 9.0.1npm install find-my-way@9.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for find-my-way, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update find-my-way to 8.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45813 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-45813 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| multicluster engine for Kubernetes 2.6 for RHEL 8 | multicluster-engine/assisted-image-service-rhel8:v2.6.4-4 | RHSA-2024:11293 |
| multicluster engine for Kubernetes 2.7 for RHEL 8 | multicluster-engine/assisted-service-8-rhel8:v2.7.2-1 | RHSA-2024:10857 |
| Red Hat Advanced Cluster Management for Kubernetes 2.11 for RHEL 9 | rhacm2/acm-cluster-permission-rhel9:v2.11.4-4 | RHSA-2024:11381 |
| Red Hat Advanced Cluster Management for Kubernetes 2.12 for RHEL 9 | rhacm2/acm-cli-rhel9:v2.12.1-4 | RHSA-2024:10865 |
| Red Hat OpenShift Dev Spaces 3 Containers | devspaces/dashboard-rhel8:3.17-25 | RHSA-2024:10236 |
Frequently Asked Questions
Is CVE-2024-45813 in your dependencies?
Find it across npm, including transitive dependencies.