Unsound HighRUSTSEC-2019-0011 · memoffset
RUSTSEC-2019-0011: Flaw in offset_of and span_of causes SIGILL, drops uninitialized memory of arbitrary type on panic in client code
Short answermemoffset has an API that can cause undefined behaviour from safe code: Flaw in offset_of and span_of causes SIGILL, drops uninitialized memory of arbitrary type on panic in client code. Fixed in 0.5.0.
| Crate | memoffset |
|---|---|
| Type | Unsound |
| Affected versions | Before 0.5.0. |
| Fixed in | 0.5.0 |
| Severity | High, CVSS 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| Published | 2019-07-16 |
| Last changed | 2023-11-08 |
| Also known as | CVE-2019-15553, GHSA-rh89-x75f-rh3c |
What to do
- See which version you have:
cargo tree -i memoffset(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p memoffset. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplememoffset = "0.5.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
Affected versions of this crate caused traps and/or memory unsafety by zero-initializing references. They also could lead to uninitialized memory being dropped if the field for which the offset is requested was behind a deref coercion, and that deref coercion caused a panic.
The flaw was corrected by using MaybeUninit.
References
- Package: crates.io/crates/memoffset
- Advisory: rustsec.org/advisories/RUSTSEC-2019-0011.html
- Report: github.com/Gilnaa/memoffset/issues/9#issuecomment-505461490
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for memoffset
Up next
Same cratememoffset: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?