Undefined behavior via uninitialized generic values
Published Dec 26, 2021 · Updated Nov 18, 2024
Use of uninitialized memory in the smallvec crate before 0.6.13 allows attackers to create invalid values of any Rust type. Affected generic initialization calls mem::uninitialized() for a user-supplied type T, so reference types can be created without the non-null value their invariant requires. Reachability depends on downstream code instantiating and using the affected generic path; the resulting invalid value causes undefined behavior with consequences determined by that code.
Summary
What happened
Use of uninitialized memory in the smallvec crate before 0.6.13 allows attackers to create invalid values of any Rust type. Affected generic initialization calls mem::uninitialized() for a user-supplied type T, so reference types can be created without the non-null value their invariant requires. Reachability depends on downstream code instantiating and using the affected generic path; the resulting invalid value causes undefined behavior with consequences determined by that code.
The record
- CVE
- CVE-2018-25023
- Published
- Dec 26, 2021
- Updated
- Nov 18, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2021CVE publishedPublication date reported by the CVE source.
- Nov 18, 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.
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