Memory corruption via partially uninitialized array drop
Published Jan 22, 2021 · Updated Aug 4, 2024
Memory corruption in the autorand crate before 0.2.3 allows local users to trigger undefined behavior through a panicking Random implementation. The array Random implementation allocates an uninitialized array and drops partially initialized elements if user-defined T::random() panics. Exploitation requires code that invokes Random for arrays with an attacker-controlled implementation; the invalid drop can corrupt memory or crash the process.
Summary
What happened
Memory corruption in the autorand crate before 0.2.3 allows local users to trigger undefined behavior through a panicking Random implementation. The array Random implementation allocates an uninitialized array and drops partially initialized elements if user-defined T::random() panics. Exploitation requires code that invokes Random for arrays with an attacker-controlled implementation; the invalid drop can corrupt memory or crash the process.
The record
- CVE
- CVE-2020-36210
- Published
- Jan 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-908
- Attack vector
- local
- Privileges
- Unavailable
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.
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.
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