Application crashes via unconstrained Ptr thread-safety traits
Published Aug 8, 2021 · Updated Aug 4, 2024
A data race in Ptr in the cgc crate 0.4.0 and earlier allows attackers to crash applications through concurrent use. The Ptr type unconditionally implements Send and Sync for every T, so non-thread-safe values such as Rc and Cell can cross thread boundaries and be accessed concurrently. Reachability requires consuming code to share Ptr-held non-thread-safe values across threads; the published proof of concept demonstrates a segmentation fault, while no confidentiality or integrity impact is reported.
Summary
What happened
A data race in Ptr in the cgc crate 0.4.0 and earlier allows attackers to crash applications through concurrent use. The Ptr type unconditionally implements Send and Sync for every T, so non-thread-safe values such as Rc and Cell can cross thread boundaries and be accessed concurrently. Reachability requires consuming code to share Ptr-held non-thread-safe values across threads; the published proof of concept demonstrates a segmentation fault, while no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2020-36466
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1499.004
- 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
- Soundness issues with Ptr proof of conceptproof 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