Rust advisories / ash
Unsound CriticalRUSTSEC-2021-0090 · ash
RUSTSEC-2021-0090: Reading on uninitialized memory may cause UB ( `util::read_spv()` )
Short answerash has an API that can cause undefined behaviour from safe code: Reading on uninitialized memory may cause UB ( `util::read_spv()` ). Fixed in 0.33.1.
| Crate | ash |
|---|---|
| Type | Unsound (memory-exposure) |
| Affected versions | Before 0.33.1. |
| Fixed in | 0.33.1 |
| Severity | Critical (GitHub rating) |
| Published | 2021-01-07 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2021-45688, GHSA-64wv-8vwp-xgw2, GHSA-qj69-c89v-jwq2 |
What to do
- See which version you have:
cargo tree -i ash(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p ash. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleash = "0.33.1") 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 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/ash
- Advisory: rustsec.org/advisories/RUSTSEC-2021-0090.html
- Report: github.com/MaikKlein/ash/issues/354
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?