Memory corruption via unsound World Send implementation
Published Aug 8, 2021 · Updated Aug 4, 2024
Data race in dces 0.3.0 and earlier allows attackers to corrupt memory by moving a World with non-thread-safe stores across threads. World is marked Send without requiring EntityStore and ComponentStore implementations to be Send, so Rust permits their cross-thread transfer. Exploitation requires code to instantiate World with non-thread-safe stores and move it between threads, where concurrent access can corrupt memory or crash the consuming process.
Summary
What happened
Data race in dces 0.3.0 and earlier allows attackers to corrupt memory by moving a World with non-thread-safe stores across threads. World is marked Send without requiring EntityStore and ComponentStore implementations to be Send, so Rust permits their cross-thread transfer. Exploitation requires code to instantiate World with non-thread-safe stores and move it between threads, where concurrent access can corrupt memory or crash the consuming process.
The record
- CVE
- CVE-2020-36459
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, CWE-77
- 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
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