Integrity bypass via leading protocol whitespace
Published Mar 3, 2022 · Updated Apr 22, 2025
Improper input validation in URI.js before 1.19.9 allows remote attackers to alter protocol interpretation via leading whitespace. URI.parse receives input without stripping leading whitespace, so protocol validation mechanisms can accept a URL differently from its intended scheme. The issue requires an application to pass attacker-controlled URL text to URI.js and can enable integrity-impacting validation bypass without reported confidentiality or availability impact.
Summary
What happened
Improper input validation in URI.js before 1.19.9 allows remote attackers to alter protocol interpretation via leading whitespace. URI.parse receives input without stripping leading whitespace, so protocol validation mechanisms can accept a URL differently from its intended scheme. The issue requires an application to pass attacker-controlled URL text to URI.js and can enable integrity-impacting validation bypass without reported confidentiality or availability impact.
The record
- CVE
- CVE-2022-24723
- Published
- Mar 3, 2022
- Updated
- Apr 22, 2025
- Vendor
- medialize
- Product
- URI.js
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.19.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo