uri.js_project 関連製品全体の CVE とセキュリティ脆弱性情報を集約し、CVSS、EPSS、公開日、脆弱性情報データを掲載しています。
公開された問題は vendor risk open redirect and vendor risk input validation に関連することが多く、vendor surface software deployment and vendor surface production workloads の文脈で vendor impact unexpected behavior などの暴露リスクを伴う場合があります。
掲載データは公開脆弱性情報とセキュリティ公告に基づき、過去の暴露面と修補優先度の評価に利用できます。
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| 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.64% | 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.76% | 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.71% | 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 | 1.99% | 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 | 1.58% | 2022-02-16 | 2024-11-21 |
| CVE-2021-3647 | URI.js is vulnerable to URL Redirection to Untrusted Site | [email protected] | 6.1 | 0.91% | 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 | 2.48% | 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 | 1.69% | 2020-12-31 | 2024-11-21 |