Application crash via invalid empty-segment free
Published Jan 6, 2022 · Updated Aug 4, 2024
Use-after-free in uriparser before 0.9.6 allows local users to crash a consuming application by triggering URI normalization. When normalization of an empty URI segment encounters an allocation failure, uriPreventLeakage treats non-heap-backed text as owned and passes it to the configured free callback. Exploitation requires a consuming application to normalize a URI containing empty segments during an allocation failure, and user interaction is required.
Summary
What happened
Use-after-free in uriparser before 0.9.6 allows local users to crash a consuming application by triggering URI normalization. When normalization of an empty URI segment encounters an allocation failure, uriPreventLeakage treats non-heap-backed text as owned and passes it to the configured free callback. Exploitation requires a consuming application to normalize a URI containing empty segments during an allocation failure, and user interaction is required.
The record
- CVE
- CVE-2021-46142
- Published
- Jan 6, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 6, 2022CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- uriNormalizeSyntax AddressSanitizer reproducerproof of concept · demonstrated
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