Rust advisories / out-reference
Unsound MediumRUSTSEC-2021-0152 · out-reference
RUSTSEC-2021-0152: `out_reference::Out::from_raw` should be `unsafe`
Short answerout-reference has an API that can cause undefined behaviour from safe code: `out_reference::Out::from_raw` should be `unsafe`. Fixed in 0.2.0.
| Crate | out-reference |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | From 0.1.0 before 0.2.0. |
| Fixed in | 0.2.0 |
| Severity | Medium (GitHub rating) |
| Published | 2021-01-20 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-p7mj-xvxg-grff |
| Affected functions | out_reference::Out::from_raw |
What to do
- See which version you have:
cargo tree -i out-reference(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p out-reference. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for exampleout-reference = "0.2.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
Out::from_raw in affected versions allows writing a value to invalid memory address without requiring unsafe.
The soundness issue has been addressed by making Out::from_raw an unsafe function.
References
- Package: crates.io/crates/out-reference
- Advisory: rustsec.org/advisories/RUSTSEC-2021-0152.html
- Report: github.com/RustyYato/out-ref/issues/1
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?