Rust advisories / mod3d-base
UnsoundRUSTSEC-2025-0171 · mod3d-base
RUSTSEC-2025-0171: soundness issue
Short answermod3d-base has an API that can cause undefined behaviour from safe code: soundness issue. Fixed in 0.3.0.
| Crate | mod3d-base |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Before 0.3.0. |
| Fixed in | 0.3.0 |
| Severity | not scored |
| Published | 2025-05-06 |
| Last changed | 2026-08-31 |
| Also known as | none |
| Affected functions | mod3d_base::BufferData::as_ptr |
What to do
- See which version you have:
cargo tree -i mod3d-base(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p mod3d-base. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplemod3d-base = "0.3.0") 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
mod3d_base::BufferData::as_ptr lack of sufficient checks to its public self field byte_offset and used unsafely to do the pointer calculation.
References
- Package: crates.io/crates/mod3d-base
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0171.html
- Web: github.com/atthecodeface/model3d
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?