Memory corruption via unsound AtomicBox thread traits
Published Aug 8, 2021 · Updated Aug 4, 2024
Thread-safety flaws in the abox crate before 0.4.1 allow attackers to trigger undefined behavior through safe Rust code. AtomicBox implements Send and Sync for every sized T without the trait bounds required for safe cross-thread transfer and sharing. A consuming program must use AtomicBox with a non-Send or non-Sync type across threads; the resulting data race can corrupt memory or crash the process.
Summary
What happened
Thread-safety flaws in the abox crate before 0.4.1 allow attackers to trigger undefined behavior through safe Rust code. AtomicBox implements Send and Sync for every sized T without the trait bounds required for safe cross-thread transfer and sharing. A consuming program must use AtomicBox with a non-Send or non-Sync type across threads; the resulting data race can corrupt memory or crash the process.
The record
- CVE
- CVE-2020-36441
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, CWE-119
- 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.
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
Public exploit references
- AtomicBox Cell data-race demonstrationproof 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