Security-check bypass via leading-whitespace URL parsing
Published Feb 4, 2020 · Updated Aug 4, 2024
Improper input validation in Unshift.io url-parse 1.4.4 and earlier allows remote attackers to bypass security checks via crafted URLs. The extractProtocol and Url parser paths failed to remove leading whitespace before interpreting protocol and hostname data, so specially prefixed URLs could produce false security decisions. Exploitation requires an application to pass attacker-controlled URLs into the library; the bounded impact is integrity loss in those checks, including possible redirect or request-policy bypasses.
Summary
What happened
Improper input validation in Unshift.io url-parse 1.4.4 and earlier allows remote attackers to bypass security checks via crafted URLs. The extractProtocol and Url parser paths failed to remove leading whitespace before interpreting protocol and hostname data, so specially prefixed URLs could produce false security decisions. Exploitation requires an application to pass attacker-controlled URLs into the library; the bounded impact is integrity loss in those checks, including possible redirect or request-policy bypasses.
The record
- CVE
- CVE-2020-8124
- Published
- Feb 4, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unshift.io
- Product
- url-parse
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=Fixed Version 1.4.5
What conditions does exploitation require?
What is affected?
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