~ / search / GHSA-8v38-pw62-9cw2

GHSA-8v38-pw62-9cw2

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

Source: GitHub Advisory Database (reviewed) Moderate CVE-2022-0639

Packages

EcosystemPackageAffectedFixed in
npm url-parse >= 1.0.0, < 1.5.7 1.5.7

Details

As written in the advisory (Markdown source, shown as plain text).

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.

References

External links from the advisory. They lead to third-party sites.