`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
Résumé
serde deserialization for FamStructWrapper lacks bound checks that could potentially lead to out-of-bounds memory access
Description d'origine
La description telle que publiée par la source (souvent en anglais).
Impact
An issue was discovered in the FamStructWrapper::deserialize implementation
provided by the crate for vmm_sys_util::fam::FamStructWrapper, which can lead
to out of bounds memory accesses. The deserialization does not check that the
length stored in the header matches the flexible array length. Mismatch in the
lengths might allow out of bounds memory access through Rust-safe methods.
Impacted versions: >= 0.5.0
Patches
The issue was corrected in version 0.12.0 by inserting a check that verifies
the lengths of compared flexible arrays are equal for any deserialized header
and aborting deserialization otherwise. Moreover, the API was changed so that
header length can only be modified through Rust-unsafe code. This ensures that
users cannot trigger out-of-bounds memory access from Rust-safe code.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Paquets affectés
État des correctifs par distribution
Paquets corrigés publiés par chaque distribution pour cette CVE
- Debian DEBIAN-CVE-2023-50711 rust-vmm-sys-util Corrigé dans: 0.12.1-1
- Ubuntu UBUNTU-CVE-2023-50711 rust-vmm-sys-util
Références
- advisory rustsec.org
- package crates.io
- web github.com