Advisory

GHSA-49hh-fprx-m68g

Also known as: CVE-2023-41051, RUSTSEC-2023-0056

Summary

Default functions in VolatileMemory trait lack bounds checks, potentially leading to out-of-bounds memory accesses

Details

Impact
An issue was discovered in the default implementations of the VolatileMemory::{get_atomic_ref, aligned_as_ref, aligned_as_mut, get_ref, get_array_ref} trait functions, which allows out-of-bounds memory access if the VolatileMemory::get_slice function returns a VolatileSlice whose length is less than the function’s count argument. No implementations of get_slice provided in vm_memory are affected. Users of custom VolatileMemory implementations may be impacted if the custom implementation does not adhere to get_slice's documentation.

Patches
The issue started in version 0.1.0 but was fixed in version 0.12.2 by inserting a check that verifies that the VolatileSlice returned by get_slice is of the correct length.

Workarounds
Not Required

References
https://github.com/rust-vmm/vm-memory/commit/aff1dd4a5259f7deba56692840f7a2d9ca34c9c8
https://crates.io/crates/vm-memory/0.12.2

Severity

Low Basis: The source's own band: LOW

Dates

Published
2023-09-04 16:35 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

vm-memory

crates.io · All systems

Affected

  • introduced 0, fixed 0.12.2 (semver)

Fixed versions

0.12.2

Fix

  • Fixed version 0.12.2
    cargo update -p vm-memory --precise 0.12.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences