Bug 1800774 (CVE-2020-8124) - CVE-2020-8124 npmjs-url-parse: Improper validation of protocol of the returned URL
Summary: CVE-2020-8124 npmjs-url-parse: Improper validation of protocol of the returne...
Alias: CVE-2020-8124
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1802346
Blocks: 1800776
TreeView+ depends on / blocked
Reported: 2020-02-07 20:55 UTC by Pedro Sampaio
Modified: 2020-12-15 16:01 UTC (History)
7 users (show)

Fixed In Version: nodejs-url-parse 1.4.5
Doc Type: If docs needed, set a value
Doc Text:
An input validation flaw exists in the node.js-url-parse, which results in the URL being incorrectly set to the document location protocol instead of the URL being passed as an argument. An attacker could use this flaw to bypass security checks on URLs.
Clone Of:
Last Closed: 2020-03-25 22:31:51 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:0972 0 None None None 2020-03-25 19:33:14 UTC

Description Pedro Sampaio 2020-02-07 20:55:26 UTC
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.



Comment 4 Jason Shepherd 2020-02-13 00:02:24 UTC
Created nodejs-url-parse-lax tracking bugs for this issue:

Affects: epel-7 [bug 1802346]

Comment 5 Mark Cooper 2020-03-02 00:55:27 UTC
OpenShift ServiceMesh is packaging a vulnerable version of nodejs url-parse (1.4.4) in the container:
    - distributed-tracing/jaeger-rhel7-operator

Also found in the kiali rpm.

The grafana component included within ServiceMesh itself, also includes url-parse but is version 1.4.7 and is not vulnerable.

Comment 9 errata-xmlrpc 2020-03-25 19:33:12 UTC
This issue has been addressed in the following products:

  Openshift Service Mesh 1.0

Via RHSA-2020:0972 https://access.redhat.com/errata/RHSA-2020:0972

Comment 10 Product Security DevOps Team 2020-03-25 22:31:51 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.