Rust advisories / bite
Unsound HighRUSTSEC-2020-0153 · bite
RUSTSEC-2020-0153: `read` on uninitialized buffer may cause UB (bite::read::BiteReadExpandedExt::read_framed_max)
Short answerbite has an API that can cause undefined behaviour from safe code: `read` on uninitialized buffer may cause UB (bite::read::BiteReadExpandedExt::read_framed_max). No fixed version yet.
| Crate | bite |
|---|---|
| Type | Unsound (memory-exposure) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | High (GitHub rating) |
| Published | 2020-12-31 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36511, GHSA-72r2-rg28-47v9, GHSA-v2ch-fc8f-qm33 |
What to do
- Find who pulls it in:
cargo tree -i bite. - Avoid the affected API, or replace the crate.
Details from the advisory
Affected versions of this crate calls a user provided Read implementation on an uninitialized buffer.
Read on uninitialized buffer is defined as undefined behavior in Rust.
References
- Package: crates.io/crates/bite
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0153.html
- Report: github.com/hinaria/bite/issues/1
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?