Code execution via assumed trait-object layout
Published Dec 26, 2021 · Updated Aug 4, 2024
Memory unsoundness in mopa 0.2.2 and earlier allows attackers to expose ASLR addresses or execute code after a trait-layout change. Its downcasting methods transmute trait-object references into a hand-defined structure and treat the resulting fields as data and vtable pointers, although Rust does not guarantee that layout. Exploitation requires a compiler that changes the assumed field order and a consuming application path that performs an affected downcast; Rust 1.52 retained the assumed layout.
Summary
What happened
Memory unsoundness in mopa 0.2.2 and earlier allows attackers to expose ASLR addresses or execute code after a trait-layout change. Its downcasting methods transmute trait-object references into a hand-defined structure and treat the resulting fields as data and vtable pointers, although Rust does not guarantee that layout. Exploitation requires a compiler that changes the assumed field order and a consuming application path that performs an affected downcast; Rust 1.52 retained the assumed layout.
The record
- CVE
- CVE-2021-45695
- Published
- Dec 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 26, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No sourced classifications are available.
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