Memory corruption via unsound Send and Sync
Published Jan 22, 2021 · Updated Aug 4, 2024
Memory corruption in the aovec crate 1.1.0 and earlier allows local users to trigger undefined behavior through cross-thread use. Aovec implements Send and Sync for every T without requiring T to implement the corresponding trait, so Rc and Cell values can cross thread boundaries unsafely. Exploitation requires low-privileged local code to exercise concurrent access, causing data races that can corrupt memory.
Summary
What happened
Memory corruption in the aovec crate 1.1.0 and earlier allows local users to trigger undefined behavior through cross-thread use. Aovec implements Send and Sync for every T without requiring T to implement the corresponding trait, so Rc and Cell values can cross thread boundaries unsafely. Exploitation requires low-privileged local code to exercise concurrent access, causing data races that can corrupt memory.
The record
- CVE
- CVE-2020-36207
- Published
- Jan 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-662, CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 22, 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.
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