# CVE-2022-24723: Improper Input Validation in URI.js

> URI.js fails to strip leading whitespace from protocols, causing improper URL parsing and potential security bypasses in applications using the library.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-gmv4-r438-p67f, UBUNTU-CVE-2022-24723

## What is CVE-2022-24723?

CVE-2022-24723 is a medium-severity vulnerability in medialize URI.js, published on 3 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-24723?

2 open source packages ship an affected version, including urijs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `urijs` | npm | All versions | 1.19.9 |
| `urijs` | npm | All versions | 1.19.9 |

Products: Uri.js Project Uri.js.

## How do I fix CVE-2022-24723?

Upgrade urijs to 1.19.9 or later.

## Is CVE-2022-24723 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24723 exists.

## Other vulnerabilities in medialize URI.js

- [CVE-2022-0868](https://insights.sbomify.com/CVE-2022-0868/): Open Redirect in medialize/uri.js (high 8.0)
- [CVE-2021-27516](https://insights.sbomify.com/CVE-2021-27516/): URIjs Hostname spoofing via backslashes in URL (high 7.5)
- [CVE-2022-1243](https://insights.sbomify.com/CVE-2022-1243/): CRHTLF can lead to invalid protocol extraction potentially leading to XSS in medialize/uri.js (high 7.2)
- [CVE-2022-1233](https://insights.sbomify.com/CVE-2022-1233/): URL Confusion When Scheme Not Supplied in medialize/uri.js (medium 6.5)
- [CVE-2020-26291](https://insights.sbomify.com/CVE-2020-26291/): Hostname spoofing in URI.js (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24723 and fix it if it is affected.

What it is: CVE-2022-24723 is a medium-severity vulnerability in medialize URI.js, published on 3 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24723 exists.

Affected packages and fixed versions:
- urijs (npm): affected all versions; fixed in 1.19.9
- urijs (npm): affected all versions; fixed in 1.19.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24723/ (Markdown: https://insights.sbomify.com/CVE-2022-24723/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24723
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24723
- OSV: https://osv.dev/vulnerability/CVE-2022-24723

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24723/
Summaries are generated and may contain mistakes; the official description above is the record.