Rust advisories / simple-slab
Vulnerability CriticalRUSTSEC-2020-0039 · simple-slab
RUSTSEC-2020-0039: `index()` allows out-of-bound read and `remove()` has off-by-one error
Short answerA security vulnerability in the simple-slab crate: `index()` allows out-of-bound read and `remove()` has off-by-one error. GitHub rates it Critical. Fixed in 0.3.3: update to a fixed version.
| Crate | simple-slab |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 0.3.3. |
| Fixed in | 0.3.3 |
| Severity | Critical (GitHub rating) |
| Published | 2020-09-03 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2020-35892, CVE-2020-35893, GHSA-438g-fx34-4h9m, GHSA-hqc8-j86x-2764 |
What to do
- See which version you have:
cargo tree -i simple-slab(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p simple-slab. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplesimple-slab = "0.3.3") 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
Slab::index() does not perform the boundary checking, which leads to out-of-bound read access. Slab::remove() copies an element from an invalid address due to off-by-one error, resulting in memory leakage and uninitialized memory drop.
References
- Package: crates.io/crates/simple-slab
- Advisory: rustsec.org/advisories/RUSTSEC-2020-0039.html
- Report: github.com/nathansizemore/simple-slab/issues/2
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?