Rust advisories / redox_uefi_std
Unsound LowRUSTSEC-2025-0032 · redox_uefi_std
RUSTSEC-2025-0032: Safe API can cause heap-buffer-overflow
Short answerredox_uefi_std has an API that can cause undefined behaviour from safe code: Safe API can cause heap-buffer-overflow. Fixed in 0.1.14.
| Crate | redox_uefi_std |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | From 0.1.8 before 0.1.14. |
| Fixed in | 0.1.14 |
| Severity | Low (GitHub rating) |
| Published | 2025-03-27 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-58xc-hpvq-8473 |
| Affected functions | redox_uefi_std::ffi::nstr |
What to do
- See which version you have:
cargo tree -i redox_uefi_std(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p redox_uefi_std. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleredox_uefi_std = "0.1.14") 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
ffi::nstr() should be marked unsafe, since a pointer to a buffer without a trailing 0 value will cause a heap buffer overflow.
References
- Package: crates.io/crates/redox_uefi_std
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0032.html
- Web: gitlab.redox-os.org/redox-os/uefi/-/commit/b711d47e815665b0ec8949e39292ad8e3fdd0756
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?