Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2022-38900

HIGH

decode-uri-component vulnerable to Denial of Service (DoS)

Also known asGHSA-w573-4hg7-7wgq
Published
Nov 28, 2022
Updated
Jul 15, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known

EPSS Exploitation Probability

via FIRST.org ↗
24.9%probability of exploitation in next 30 days
Moderate Risk98th percentile0.00%
0.00%10.8%21.5%32.3%0.6%24.9%Jan 26May 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

decode-uri-componentnpm
26.2Mdownloads / week

Description

decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdecode-uri-componentall versions0.2.1
Exploits & PoCs
2

Research 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 dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decode-uri-component. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-38900 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-38900. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
O3 Security · Impact-Aware SCA

Is CVE-2022-38900 in your dependencies?

O3 detects CVE-2022-38900 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.