GHSA-8v38-pw62-9cw2

ghsaUSosv

url-parse Incorrectly parses URLs that include an '@'

view advisory published 2022-02-18Licence: CC-BY-4.0

A specially crafted URL with an '@' sign but empty user info and no hostname, when parsed with url-parse, url-parse will return the incorrect href. In particular, ```js parse(\"http://@/127.0.0.1\") ``` Will return: ```yaml { slashes: true, protocol: 'http:', hash: '', query: '', pathname: '/127.0.0.1', auth: '', host: '', port: '', hostname: '', password: '', username: '', origin: 'null', href: 'http:///127.0.0.1' } ``` If the 'hostname' or 'origin' attributes of the output from url-parse are used in security decisions and the final 'href' attribute of the output is then used to make a request, the decision may be incorrect.

01

describes (1)

Related CVEs.

IDseverity exploitable
CVE-2022-0639USmedium5.3—
Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.7.
02

references

External citations — patches, advisories, analysis.

scry

Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.

Free scan