Undefined behavior via unconditional Send and Sync
Published Jan 22, 2021 · Updated Aug 4, 2024
Improper synchronization in the buttplug crate before 1.0.4 allows remote attackers to cause undefined behavior through concurrent use. ButtplugFutureStateShared implements Send and Sync without requiring T to implement those traits, so non-Send values cross thread boundaries and non-Sync values are shared concurrently. The condition requires a consuming application to use such a value across threads; execution then enters undefined behavior, including a data race and loss of availability.
Summary
What happened
Improper synchronization in the buttplug crate before 1.0.4 allows remote attackers to cause undefined behavior through concurrent use. ButtplugFutureStateShared implements Send and Sync without requiring T to implement those traits, so non-Send values cross thread boundaries and non-Sync values are shared concurrently. The condition requires a consuming application to use such a value across threads; execution then enters undefined behavior, including a data race and loss of availability.
The record
- CVE
- CVE-2020-36218
- Published
- Jan 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-662, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
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.
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