CVE-2022-38900 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in decode-uri-component. 2 public exploit references exist, so weaponization risk is real. A fix is available for decode-uri-component — see the affected versions and patch details below.
decode-uri-component vulnerable to Denial of Service (DoS)
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-38900.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-38900 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
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.
decode-uri-componentnpmDescription
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | decode-uri-component | all versions | 0.2.1npm install decode-uri-component@0.2.1 |
Affected Products
decode-uri-componentdecode-uri-component_projectResearch 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 decode-uri-component, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update decode-uri-component to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-38900 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.
For OpenShift Container Platform (OCP), Advanced Clusters Management for Kubernetes (ACM) and Advanced Cluster Security (ACS), the NPM decode-uri-component package is only present in source repositories as a development dependency, it is not used in production. Therefore this vulnerability is rated Low for OCP and…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | nodejs:14-8070020230306170042.bd1311ed | RHSA-2023:1743 |
| Red Hat Enterprise Linux 8.4 Extended Update Support | nodejs:14-8040020230306170312.522a0ee4 | RHSA-2023:1533 |
| Red Hat Enterprise Linux 8.6 Extended Update Support | nodejs:14-8060020230306170237.ad008a3a | RHSA-2023:1742 |
| Red Hat Enterprise Linux 9 | pcs-0:0.11.6-3.el9 | RHSA-2023:6316 |
| Red Hat Migration Toolkit for Containers 1.7 | rhmtc/openshift-migration-ui-rhel8:v1.7.8-5 | RHSA-2023:1428 |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | rh-nodejs14-0:3.6-2.el7 | RHSA-2023:1744 |
| RHODF-4.13-RHEL-9 | odf4/odf-console-rhel9:v4.13.0-85 | RHSA-2023:3742 |
| RHPAM 7.13.4 async | decode-uri-component | RHSA-2023:4983 |
Frequently Asked Questions
Is CVE-2022-38900 in your dependencies?
Find it across npm, including transitive dependencies.