Unsound MediumRUSTSEC-2023-0015 · ascii
RUSTSEC-2023-0015: Ascii allows out-of-bounds array indexing in safe code
Short answerascii has an API that can cause undefined behaviour from safe code: Ascii allows out-of-bounds array indexing in safe code. Fixed in 0.9.3.
| Crate | ascii |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | From 0.6.1 before 0.9.3. |
| Fixed in | 0.9.3 |
| Severity | Medium (GitHub rating) |
| Published | 2023-02-25 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-mrrw-grhq-86gf |
What to do
- See which version you have:
cargo tree -i ascii(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p ascii. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleascii = "0.9.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
Affected version of this crate had implementation of From<&mut AsciiStr> for &mut [u8] and &mut str. This can result in out-of-bounds array indexing in safe code.
The flaw was corrected in commit 8a6c779 by removing those impls.
References
- Package: crates.io/crates/ascii
- Advisory: rustsec.org/advisories/RUSTSEC-2023-0015.html
- Report: github.com/tomprogrammer/rust-ascii/issues/64
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
Same crateascii: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?