Skip to content
Fencer Intel
medium 5.3

CVE-2020-8124 json

Improper Validation and Sanitization in url-parse

published 6y ago modified 4mo ago also GHSA-46c4-8wrp-j99v , EUVD-2022-0441

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 76%
public exploits
0
none known

Summary

Insufficient validation and sanitization of user input exists in url-parse npm package version 1.4.4 and earlier may allow attacker to bypass security checks.

Patch / fix

  • npm url-parse 1.4.5
  • node-url-parse Debian 14, Debian 13, Debian 12 1.4.7-1

debian advisories DEBIAN-CVE-2020-8124

  • node-url-parse Ubuntu 18.04 LTS 1.2.0-1ubuntu0.1
  • node-url-parse Ubuntu Pro 16.04 LTS 1.0.5-2ubuntu0.1~esm2

ubuntu advisories UBUNTU-CVE-2020-8124

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

  • kiali service mesh 1.0 v1.0.10.redhat1-1.el7
  • jaeger service mesh 1.0 v1.13.1.redhat6-1.el7

red hat advisories RHSA-2020:0972

Is CVE-2020-8124 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 Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-8124 updated cvss 5.3

npmjs-url-parse: Improper validation of protocol of the returned URL

  • Red Hat Quay 3 nodejs-url-parse
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Service Mesh 1.0 kiali v1.0.10.redhat1-1.el7, jaeger v1.13.1.redhat6-1.el7
    fixed: vendor fix RHSA-2020:0972
  • Red Hat Distributed Tracing Jaeger 1 jaeger Red Hat OpenShift Service Mesh 1 grafana
    not 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.65% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • hackerone.com https://hackerone.com/reports/496293 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
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.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm url-parse
>=0.1.0, <1.4.5
1.4.5

Affected products

  • n/a url-parse

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

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.