Memory corruption via missing Send bound
Published Jan 22, 2021 · Updated Aug 3, 2024
Data race in the lazy-init crate before 0.4.0 allows attackers to cause memory corruption by sharing a Lazy value across threads. Lazy's unsafe Sync implementation omits a required Send bound on its stored type, so safe code can transfer a Sync but non-Send value between threads. Exploitation requires a consuming Rust program to instantiate Lazy with such a type and exercise it concurrently; resulting behavior can corrupt memory or interrupt the process.
Summary
What happened
Data race in the lazy-init crate before 0.4.0 allows attackers to cause memory corruption by sharing a Lazy value across threads. Lazy's unsafe Sync implementation omits a required Send bound on its stored type, so safe code can transfer a Sync but non-Send value between threads. Exploitation requires a consuming Rust program to instantiate Lazy with such a type and exercise it concurrently; resulting behavior can corrupt memory or interrupt the process.
The record
- CVE
- CVE-2021-25901
- Published
- Jan 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 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
- Issue 9 cross-thread transfer 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