Memory corruption via unconditional Send/Sync implementations
Published Aug 8, 2021 · Updated Aug 4, 2024
Memory corruption in bunch 0.1.0 allows attackers to trigger undefined behavior through concurrent access to Bunch values. The crate unsafely implements Send and Sync for every T without requiring T: Send or T: Sync, so Bunch::get can expose non-Sync values to simultaneous threads. Exploitation requires application code to store a non-thread-safe type and access it concurrently, producing a data race that can crash the process or corrupt memory.
Summary
What happened
Memory corruption in bunch 0.1.0 allows attackers to trigger undefined behavior through concurrent access to Bunch values. The crate unsafely implements Send and Sync for every T without requiring T: Send or T: Sync, so Bunch::get can expose non-Sync values to simultaneous threads. Exploitation requires application code to store a non-thread-safe type and access it concurrently, producing a data race that can crash the process or corrupt memory.
The record
- CVE
- CVE-2020-36450
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, CWE-362
- Attack vector
- Unavailable
- Privileges
- Unavailable
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
- Contrived multithreaded Bunch data-race 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