Memory corruption via non-atomic pointer writes
Published Aug 8, 2021 · Updated Aug 4, 2024
Data race in the cgc crate 0.4.0 and earlier allows attackers to corrupt memory through concurrent Ptr::write calls. Ptr::write replaces the underlying pointer with a non-atomic write even though Ptr can be shared across threads, allowing simultaneous accesses to race. The flaw requires a dependent program to share the same Ptr across threads and invoke Ptr::write concurrently; single-threaded use does not trigger this condition.
Summary
What happened
Data race in the cgc crate 0.4.0 and earlier allows attackers to corrupt memory through concurrent Ptr::write calls. Ptr::write replaces the underlying pointer with a non-atomic write even though Ptr can be shared across threads, allowing simultaneous accesses to race. The flaw requires a dependent program to share the same Ptr across threads and invoke Ptr::write concurrently; single-threaded use does not trigger this condition.
The record
- CVE
- CVE-2020-36468
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-657
- 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