Show filters
8 Total Results
Displaying 1-8 of 8
Sort by:
Attacker Value
Unknown

CVE-2022-1243

Disclosure Date: April 05, 2022 (last updated October 07, 2023)
CRHTLF can lead to invalid protocol extraction potentially leading to XSS in GitHub repository medialize/uri.js prior to 1.19.11.
Attacker Value
Unknown

CVE-2022-1233

Disclosure Date: April 04, 2022 (last updated October 07, 2023)
URL Confusion When Scheme Not Supplied in GitHub repository medialize/uri.js prior to 1.19.11.
Attacker Value
Unknown

CVE-2022-0868

Disclosure Date: March 06, 2022 (last updated February 23, 2025)
Open Redirect in GitHub repository medialize/uri.js prior to 1.19.10.
Attacker Value
Unknown

CVE-2022-24723

Disclosure Date: March 03, 2022 (last updated February 23, 2025)
URI.js is a Javascript URL mutation library. Before version 1.19.9, whitespace characters are not removed from the beginning of the protocol, so URLs are not parsed properly. This issue has been patched in version 1.19.9. Removing leading whitespace from values before passing them to URI.parse can be used as a workaround.
Attacker Value
Unknown

CVE-2022-0613

Disclosure Date: February 16, 2022 (last updated February 23, 2025)
Authorization Bypass Through User-Controlled Key in NPM urijs prior to 1.19.8.
Attacker Value
Unknown

CVE-2021-3647

Disclosure Date: July 16, 2021 (last updated February 23, 2025)
URI.js is vulnerable to URL Redirection to Untrusted Site
Attacker Value
Unknown

CVE-2021-27516

Disclosure Date: February 22, 2021 (last updated November 28, 2024)
URI.js (aka urijs) before 1.19.6 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relative path.
Attacker Value
Unknown

CVE-2020-26291

Disclosure Date: December 31, 2020 (last updated February 22, 2025)
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.]