Availability impact via mutable aliasing
Published Aug 8, 2021 · Updated Aug 4, 2024
Memory-safety issue in cgc crate for Rust through 0.4.0 allows attackers to cause availability impact via Ptr::get aliasing. The Ptr::get function returns multiple mutable references to the same object, violating Rust's mutable-alias rules and enabling undefined behavior when the references are used. Reaching the flaw requires code that invokes this unsafe pointer API; the published record does not establish a specific network or local attacker path, and the bounded consequence is potential service interruption or process failure.
Summary
What happened
Memory-safety issue in cgc crate for Rust through 0.4.0 allows attackers to cause availability impact via Ptr::get aliasing. The Ptr::get function returns multiple mutable references to the same object, violating Rust's mutable-alias rules and enabling undefined behavior when the references are used. Reaching the flaw requires code that invokes this unsafe pointer API; the published record does not establish a specific network or local attacker path, and the bounded consequence is potential service interruption or process failure.
The record
- CVE
- CVE-2020-36467
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-657
- 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
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