Unsound MediumRUSTSEC-2020-0097 · xcb
RUSTSEC-2020-0097: Soundness issue with base::Error
Short answerxcb has an API that can cause undefined behaviour from safe code: Soundness issue with base::Error. Fixed in 1.0.0.
| Crate | xcb |
|---|---|
| Type | Unsound (memory-corruption, thread-safety) |
| Affected versions | Before 1.0.0. |
| Fixed in | 1.0.0 |
| Severity | Medium, CVSS 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| Published | 2020-12-10 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36205, GHSA-c8hq-x4mm-p6q6 |
What to do
- See which version you have:
cargo tree -i xcb(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p xcb. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplexcb = "1.0.0") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
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.
References
- Package: crates.io/crates/xcb
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0097.html
- Report: github.com/rust-x-bindings/rust-xcb/issues/93
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for xcb
Up next
Same cratexcb: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?