Undefined behavior via unaligned TypeIdHasher pointer cast
Published Aug 8, 2021 · Updated Aug 4, 2024
Soundness violation in the anymap crate 0.12.1 and earlier allows attackers to trigger undefined behavior during type hashing. TypeIdHasher::write in src/raw.rs casts a byte-slice pointer from *const u8 to the more strictly aligned *const u64 and copies through it without ensuring eight-byte alignment. The path is reached when a consuming Rust program hashes type identifiers through the affected map, and an unaligned access produces undefined behavior.
Summary
What happened
Soundness violation in the anymap crate 0.12.1 and earlier allows attackers to trigger undefined behavior during type hashing. TypeIdHasher::write in src/raw.rs casts a byte-slice pointer from *const u8 to the more strictly aligned *const u64 and copies through it without ensuring eight-byte alignment. The path is reached when a consuming Rust program hashes type identifiers through the affected map, and an unaligned access produces undefined behavior.
The record
- CVE
- CVE-2021-38187
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-704, CWE-681
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2021CVE 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.
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