Process crash via public raw pointer
Published Jan 22, 2021 · Updated Aug 4, 2024
Memory unsafety in the Rust xcb crate before 1.0.0 allows local users to crash a consuming process through safe Rust code. The public ptr field of base::Error lets safe code construct the type with an invalid pointer; destruction can then free unowned memory, causing use-after-free or double-free. Local code execution within the consuming application is required, and the demonstrated consequence is process termination by SIGABRT.
Summary
What happened
Memory unsafety in the Rust xcb crate before 1.0.0 allows local users to crash a consuming process through safe Rust code. The public ptr field of base::Error lets safe code construct the type with an invalid pointer; destruction can then free unowned memory, causing use-after-free or double-free. Local code execution within the consuming application is required, and the demonstrated consequence is process termination by SIGABRT.
The record
- CVE
- CVE-2020-36205
- Published
- Jan 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, CWE-416
- Attack vector
- local
- Privileges
- authenticated
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.
Public exploit references
- base::Error safe-Rust use-after-free proof of conceptproof of concept · demonstrated
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