RUSTSEC-2023-0030: `Versionize::deserialize` implementation for `FamStructWrapper<T>` is lacking bound checks, potentially leading to out of bounds memory accesses

What to do

1. See which version you have: cargo tree -i versionize (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p versionize. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example versionize = "0.1.10") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

An issue was discovered in the Versionize::deserialize implementation provided by the versionize crate for vmm_sys_util::fam::FamStructWrapper, which can lead to out of bounds memory accesses. The impact started with version 0.1.1. The issue was corrected in version 0.1.10 by inserting a check that verifies, for any deserialized header, the lengths of compared flexible arrays are equal and aborting deserialization otherwise.

References

• Package: crates.io/crates/versionize
• Advisory: rustsec.org/advisories/RUSTSEC-2023-0030.html
• Web: github.com/firecracker-microvm/versionize/pull/53

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.