CVE-2022-0691 | Authorization Bypass Through User-Controlled Key in unshiftio/url-parse

Exp

Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.9.

Published: 2022-02-21 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-0691 is rated High Exploit Risk (64.5/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.11%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-0691

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-0691

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.28% 0.11% -0.18%
2 2025-11-18 0.12% 0.28% +0.16%
3 2025-07-19 — 0.12% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-0691

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
6.5 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 2.5 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2022-0691

GitHub Security Advisory for CVE-2022-0691

GHSA-jf5r-8hm2-f872 · Severity: medium · Ecosystem: npm — url-parse incorrectly parses hostname / protocol due to unstripped leading control characters.

OS Trackers for CVE-2022-0691

vendor priority summary link
debian not yet assigned CVE-2022-0691 not yet assigned priority: Debian including 1 source packages (node-url-parse), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-0691
redhat high — https://access.redhat.com/security/cve/CVE-2022-0691
ubuntu medium CVE-2022-0691 medium priority: Ubuntu including 1 source packages (node-url-parse), 9 status rows across 9 suites (bionic, focal, impish, jammy, kinetic, lunar, trusty, upstream, xenial): released 4, not-affected 3, ignored 2. https://ubuntu.com/security/CVE-2022-0691

Affected software / configurations for CVE-2022-0691

Vendor Product Version Raw CPE
url-parse_project url-parse < 1.5.9 cpe:2.3:a:url-parse_project:url-parse:*:*:*:*:*:node.js:*:*

References for CVE-2022-0691

cvelogic Threat Intelligence