Memory corruption via unchecked Send and Sync bounds
Published Dec 26, 2021 · Updated Aug 4, 2024
Memory corruption in the metrics-util crate before 0.7.0 allows attackers to trigger a data race through AtomicBucket::data_with(). AtomicBucket's internal Block implements Send and Sync without requiring T to satisfy the corresponding trait bound, so data_with() can expose a non-Sync value across threads. Exploitation requires application code to place a non-Sync value in an AtomicBucket and invoke the API concurrently, producing undefined behavior that can corrupt memory.
Summary
What happened
Memory corruption in the metrics-util crate before 0.7.0 allows attackers to trigger a data race through AtomicBucket::data_with(). AtomicBucket's internal Block implements Send and Sync without requiring T to satisfy the corresponding trait bound, so data_with() can expose a non-Sync value across threads. Exploitation requires application code to place a non-Sync value in an AtomicBucket and invoke the API concurrently, producing undefined behavior that can corrupt memory.
The record
- CVE
- CVE-2021-45704
- Published
- Dec 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-362
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 26, 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