CVE-2023-41051

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

Workarounds

Not Required

References

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

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.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

CVE-2023-41051 has a CVSS score of 2.5 (Low). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.12.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is CVE-2023-41051? CVE-2023-41051 is a low-severity out-of-bounds read vulnerability in vm-memory (rust), affecting versions < 0.12.2. It is fixed in 0.12.2. A read operation accesses a memory location beyond the intended buffer boundary.
2. How severe is CVE-2023-41051? CVE-2023-41051 has a CVSS score of 2.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of vm-memory are affected by CVE-2023-41051? vm-memory (rust) versions < 0.12.2 is affected.
4. Is there a fix for CVE-2023-41051? Yes. CVE-2023-41051 is fixed in 0.12.2. Upgrade to this version or later.
5. Is CVE-2023-41051 exploitable, and should I be worried? Whether CVE-2023-41051 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-41051 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-41051? Upgrade vm-memory to 0.12.2 or later.

Other vulnerabilities in vm-memory