CVE-2020-36205
lowpriority · track · 22EPSS 0.004 · 35 %ileEUUSEPSS · scored 2026-10-27
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.1–5.5
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- GHSA-c8hq-x4mm-p6q6Memory handling issues in xcb2021-08-25ghsa · osvUS
An issue was discovered in the xcb crate through 2020-12-10 for Rust. base::Error does not have soundness. Because of the public ptr field, a use-after-free or double-free can occur.
- RUSTSEC-2020-0097Soundness issue with base::Error2020-12-10vendor · osvUS
`base::Error` type contains public field named `ptr`. With this definition, it is possible to create a `base::Error` with an invalid pointer and trigger memory safety errors such as use-after-free or double-free with safe Rust. The users of `xcb` crate are advised not to manipulate the field.
also known as (5)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (4)
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan