CVE-2020-26291: Hostname spoofing in URI.js
A flaw was found in urijs. The hostname can be spoofed by using a backslash (\) character followed by an at (@) character. If the hostname is used in security decisions, the decision may be incorrect. Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior.
Other sources
In URI.js before version 1.19.4, the hostname can be spoofed by using a backslash (\) character followed by an at (@) character. If the hostname is used in security decisions, the decision may be incorrect. Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior. For example the URL https://expected-example.com\@observed-example.com will incorrectly return observed-example.com if using an affected version. Patched versions correctly return expected-example.com. Patched versions match the behavior of other parsers which implement the WHATWG URL specification, including web browsers and Node's built-in URL class. Version 1.19.4 is patched against all known payload variants. Version 1.19.3 has a partial patch but is still vulnerable to a payload variant.]
External References:
https://github.com/medialize/URI.js/commit/b02bf037c99ac9316b77ff8bfd840e90becf1155 https://github.com/medialize/URI.js/releases/tag/v1.19.4 https://github.com/medialize/URI.js/security/advisories/GHSA-3329-pjwv-fjpg https://www.npmjs.com/package/urijs
— Red Hat
URI.js is a javascript URL mutation library (npm package urijs). In URI.js before version 1.19.4, the hostname can be spoofed by using a backslash (\) character followed by an at (@) character. If the hostname is used in security decisions, the decision may be incorrect. Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior. For example the URL https://expected-example.com\@observed-example.com will incorrectly return observed-example.com if using an affected version. Patched versions correctly return expected-example.com. Patched versions match the behavior of other parsers which implement the WHATWG URL specification, including web browsers and Node's built-in URL class. Version 1.19.4 is patched against all known payload variants. Version 1.19.3 has a partial patch but is still vulnerable to a payload variant.]
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the vulnerability ID for this flaw in urijs?
The vulnerability ID for this flaw in urijs is CVE-2020-26291.
What is the severity of CVE-2020-26291?
The severity of CVE-2020-26291 is medium with a CVSS score of 6.5.
How does the vulnerability in urijs allow hostname spoofing?
The vulnerability in urijs allows hostname spoofing by using a backslash (`\`) character followed by an at (`@`) character.
What is the affected software version of urijs?
The affected software version of urijs is version 1.19.4 and prior.
How can I fix the vulnerability in urijs?
To fix the vulnerability in urijs, update to version 1.19.4.