CVE-2022-0639 json
Authorization Bypass Through User-Controlled Key in unshiftio/url-parse
published 4y ago modified 4mo ago also GHSA-8v38-pw62-9cw2 , EUVD-2022-0924
- cvss
- 6.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.7.
Patch / fix
- npm url-parse 1.5.7
- unshiftio unshiftio/url-parse 1.5.7
- node-url-parse Debian 14, Debian 13, Debian 12 1.5.7-1
debian advisories DEBIAN-CVE-2022-0639
- node-url-parse Ubuntu 18.04 LTS 1.2.0-1ubuntu0.1
- node-url-parse Ubuntu 20.04 LTS 1.4.7-3ubuntu0.1
- node-url-parse Ubuntu Pro 16.04 LTS 1.0.5-2ubuntu0.1~esm2
ubuntu advisories UBUNTU-CVE-2022-0639
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2022-0639 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-0639 updated cvss 6.2
npm-url-parse: Authorization Bypass Through User-Controlled Key
-
Red Hat OpenShift Service Mesh 2.0 servicemesh-grafana, servicemesh-prometheus, servicemesh-grafana-prometheusaffected: no fix available
-
Red Hat OpenShift Service Mesh 2.1 servicemesh-grafanaaffected: no fix planned “Will not fix”
-
Red Hat Quay 3 quay/quay-rhel8affected: no fix available
-
Red Hat Migration Toolkit 1.7 rhmtc/openshift-migration-ui-rhel8 v1.7.4-12fixed: vendor fix RHSA-2022:6429
-
Red Hat OpenShift Service Mesh 2.1 servicemesh-prometheus Red Hat Advanced Cluster Management for Kubernetes 2 url-parse Red Hat Migration Toolkit 1.7 rhmtc/openshift-velero-plugin-rhel8 v1.7.4-6, rhmtc/openshift-migration-velero-rhel8 v1.7.4-6, rhmtc/openshift-migration-openvpn-rhel8 v1.7.4-7, rhmtc/openshift-migration-registry-rhel8 v1.7.4-7, rhmtc/openshift-migration-rhel8-operator v1.7.4-15, rhmtc/openshift-migration-controller-rhel8 v1.7.4-7, +10 more Red Hat Virtualization 4 url-parsenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.54% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/83a6bc9a-b542-4a38-82cd-d995a1481155 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | url-parse | >=1.0.0, <1.5.7 |
1.5.7 |
Affected products
- unshiftio unshiftio/url-parse
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/unshiftio/url-parse/commit/ef45a1355375a8244063793a19059b4f62fc8788
web, patch, third-party-advisory
-
huntr.dev
/bounties/83a6bc9a-b542-4a38-82cd-d995a1481155
web, exploit, issue-tracking, patch, third-party-advisory
-
lists.debian.org
/debian-lts-announce/2023/02/msg00030.html
mailing-list, web
-
lists.debian.org
/debian-lts-announce/2025/12/msg00024.html
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-0639
advisory
-
github.com
/unshiftio/url-parse
package
Sources
- CVE List CVE-2022-0639
- GitHub Advisory GHSA-8v38-pw62-9cw2
- NVD CVE-2022-0639
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.