Rust advisories / acc_reader
Unsound CriticalRUSTSEC-2020-0155 · acc_reader
RUSTSEC-2020-0155: `Read` on uninitialized buffer in `fill_buf()` and `read_up_to()`
Short answeracc_reader has an API that can cause undefined behaviour from safe code: `Read` on uninitialized buffer in `fill_buf()` and `read_up_to()`. No fixed version yet.
| Crate | acc_reader |
|---|---|
| Type | Unsound (memory-exposure) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Critical (GitHub rating) |
| Published | 2020-12-27 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-36513, CVE-2020-36514, GHSA-799f-r78p-gq9c, GHSA-hv9v-7w3v-rj6f, GHSA-p4cr-64x4-f92f |
What to do
- Find who pulls it in:
cargo tree -i acc_reader. - Avoid the affected API, or replace the crate.
Details from the advisory
Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation.
Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.
References
- Package: crates.io/crates/acc_reader
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0155.html
- Report: github.com/netvl/acc_reader/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?