Filtered by vendor Uri.js Project
Subscriptions
Filtered by product Uri.js
Subscriptions
Total
8 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2022-24723 | 2 Redhat, Uri.js Project | 3 Acm, Jboss Fuse, Uri.js | 2024-11-21 | 5.3 Medium |
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. | ||||
CVE-2022-1243 | 1 Uri.js Project | 1 Uri.js | 2024-11-21 | 6.1 Medium |
CRHTLF can lead to invalid protocol extraction potentially leading to XSS in GitHub repository medialize/uri.js prior to 1.19.11. | ||||
CVE-2022-1233 | 1 Uri.js Project | 1 Uri.js | 2024-11-21 | 6.1 Medium |
URL Confusion When Scheme Not Supplied in GitHub repository medialize/uri.js prior to 1.19.11. | ||||
CVE-2022-0868 | 1 Uri.js Project | 1 Uri.js | 2024-11-21 | 6.1 Medium |
Open Redirect in GitHub repository medialize/uri.js prior to 1.19.10. | ||||
CVE-2022-0613 | 3 Fedoraproject, Redhat, Uri.js Project | 6 Fedora, Acm, Enterprise Linux and 3 more | 2024-11-21 | 6.5 Medium |
Authorization Bypass Through User-Controlled Key in NPM urijs prior to 1.19.8. | ||||
CVE-2021-3647 | 1 Uri.js Project | 1 Uri.js | 2024-11-21 | 6.1 Medium |
URI.js is vulnerable to URL Redirection to Untrusted Site | ||||
CVE-2021-27516 | 2 Redhat, Uri.js Project | 2 Quay, Uri.js | 2024-11-21 | 7.5 High |
URI.js (aka urijs) before 1.19.6 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relative path. | ||||
CVE-2020-26291 | 2 Redhat, Uri.js Project | 2 Quay, Uri.js | 2024-11-21 | 6.5 Medium |
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.] |
Page 1 of 1.