CVE-2022-0691

Description

Leading control characters in a URL are not stripped when passed into url-parse. This can cause input URLs to be mistakenly be interpreted as a relative URL without a hostname and protocol, while the WHATWG URL parser will trim control characters and treat it as an absolute URL. If url-parse is used in security decisions involving the hostname / protocol, and the input URL is used in a client which uses the WHATWG URL parser, the decision may be incorrect. This can also lead to a cross-site scripting (XSS) vulnerability if url-parse is used to check for the javascript: protocol in URLs. See following example: ```js const parse = require('url-parse') const express = require('express') const app = express() const port = 3000 url = parse(\"\\bjavascript:alert(1)\") console.log(url) app.get('/', (req, res) => { if (url.protocol !== \"javascript:\") {res.send(\"<a href=\\'\" + url.href + \"\\'>CLICK ME!</a>\")} }) app.listen(port, () => { console.log(`Example app listening on port ${port}`) }) ```

How to fix CVE-2022-0691

To remediate CVE-2022-0691, upgrade the affected package to a fixed version below.

• —upgrade to 1.5.3-1+deb11u1 or later
• —upgrade to 1.5.9 or later

Is CVE-2022-0691 being exploited?

Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 1.5.3-1+deb11u1
• >= 0.1.0, < 1.5.9

CVSS scores

References (8)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2022-0691
• ADVISORYsecurity-tracker.debian.org/tracker/CVE-2022-0691
• PATCHgithub.com/unshiftio/url-parse
• WEBgithub.com/github/advisory-database/pull/6765
• WEB