An issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmmsysutil::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
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.
{ "nvd_published_at": "2024-01-02T20:15:10Z", "cwe_ids": [ "CWE-787" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2024-01-02T16:28:08Z" }