Memory corruption via Rust-layout byte slices
Published Jan 29, 2021 · Updated Aug 3, 2024
Undefined behavior in raw-cpuid before 9.0.0 allows context-dependent attackers to corrupt memory or crash Rust processes through string conversion. The VendorInfo::as_string(), SoCVendorBrand::as_string(), and ExtendedFunctionInfo::processor_brand_string() methods create byte slices with std::slice::from_raw_parts() over repr(Rust) structs whose layout is not guaranteed. Affected code must run on x86 or x86_64 and invoke an affected method; the resulting undefined behavior can corrupt memory or interrupt the process.
Summary
What happened
Undefined behavior in raw-cpuid before 9.0.0 allows context-dependent attackers to corrupt memory or crash Rust processes through string conversion. The VendorInfo::as_string(), SoCVendorBrand::as_string(), and ExtendedFunctionInfo::processor_brand_string() methods create byte slices with std::slice::from_raw_parts() over repr(Rust) structs whose layout is not guaranteed. Affected code must run on x86 or x86_64 and invoke an affected method; the resulting undefined behavior can corrupt memory or interrupt the process.
The record
- CVE
- CVE-2021-26306
- Published
- Jan 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, CWE-198, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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