Rust advisories / wrflib
Unsound LowRUSTSEC-2025-0072 · wrflib
RUSTSEC-2025-0072: soundness issue and unmaintained
Short answerwrflib has an API that can cause undefined behaviour from safe code: soundness issue and unmaintained. No fixed version yet.
| Crate | wrflib |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Low (GitHub rating) |
| Published | 2025-10-02 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-466c-pfvv-v83g |
| Affected functions | wrflib::byte_extract::get_f32_le, wrflib::byte_extract::get_f32_le_as_f32, wrflib::byte_extract::get_f64_le, wrflib::byte_extract::get_f64_le_as_f32, wrflib::byte_extract::get_i16_le, wrflib::byte_extract::get_i16_le_as_f32, wrflib::byte_extract::get_i32_le, wrflib::byte_extract::get_i32_le_as_f32, wrflib::byte_extract::get_i64_le, wrflib::byte_extract::get_i64_le_as_f32, wrflib::byte_extract::get_i8_le, wrflib::byte_extract::get_i8_le_as_f32 |
What to do
- Find who pulls it in:
cargo tree -i wrflib. - Avoid the affected API (
wrflib::byte_extract::get_f32_le,wrflib::byte_extract::get_f32_le_as_f32,wrflib::byte_extract::get_f64_le,wrflib::byte_extract::get_f64_le_as_f32,wrflib::byte_extract::get_i16_le,wrflib::byte_extract::get_i16_le_as_f32), or replace the crate.
Details from the advisory
All functions under wrflib::byte_extract are simply wrapper of unsafe pointer offset and lacks sufficient checks to it pointer and offset parameter.
wrflib is unmaintained.
References
- Package: crates.io/crates/wrflib
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0072.html
- Web: github.com/cruise-automation/webviz-rust-framework
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?