vm-memory
Affected
- introduced
0.0.0-0, fixed0.12.2(semver)
Fixed versions
0.12.2
Fix
- Fixed version
0.12.2cargo update -p vm-memory --precise 0.12.2
Advisory
Also known as: CVE-2023-41051, GHSA-49hh-fprx-m68g
Default functions in VolatileMemory trait lack bounds checks, potentially leading to out-of-bounds memory accesses
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.
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.
Low Basis: CVSS v3 score 2.5, vector CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L
0.0.0-0, fixed 0.12.2 (semver)0.12.2
0.12.2cargo update -p vm-memory --precise 0.12.2Fix 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
Source: RustSec Advisory Database · CC0-1.0