Aggregates CVE and security vulnerability intelligence across all uri.js_project-related products, including CVSS, EPSS, publication dates, and vulnerability intelligence data.
Disclosed issues often relate to vendor risk open redirect and vendor risk input validation; exposure may include vendor impact unexpected behavior in vendor surface software deployment contexts.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2022-1243 | CRHTLF can lead to invalid protocol extraction potentially leading to XSS in GitHub repository medialize/uri.js prior to 1.19.11. | [email protected] | 6.1 | 0.34% | 2022-04-05 | 2024-11-21 |
| CVE-2022-1233 | URL Confusion When Scheme Not Supplied in GitHub repository medialize/uri.js prior to 1.19.11. | [email protected] | 6.1 | 0.17% | 2022-04-04 | 2024-11-21 |
| CVE-2022-0868 | Open Redirect in GitHub repository medialize/uri.js prior to 1.19.10. | [email protected] | 6.1 | 0.31% | 2022-03-06 | 2024-11-21 |
| CVE-2022-24723 | 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. | [email protected] | 5.3 | 0.49% | 2022-03-03 | 2024-11-21 |
| CVE-2022-0613 | Authorization Bypass Through User-Controlled Key in NPM urijs prior to 1.19.8. | [email protected] | 6.5 | 0.08% | 2022-02-16 | 2024-11-21 |
| CVE-2021-3647 | URI.js is vulnerable to URL Redirection to Untrusted Site | [email protected] | 6.1 | 0.18% | 2021-07-16 | 2024-11-21 |
| CVE-2021-27516 | URI.js (aka urijs) before 1.19.6 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relative path. | [email protected] | 7.5 | 0.55% | 2021-02-22 | 2024-11-21 |
| CVE-2020-26291 | 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.co | [email protected] | 6.5 | 0.58% | 2020-12-31 | 2024-11-21 |