{"id":"GHSA-49hh-fprx-m68g","revision":null,"records":[{"revision":"15b56add54ab40b29ac606c1520dc36b","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2023-41051","aliases":[],"title":"Default functions in VolatileMemory trait lack bounds checks in vm-memory","description":"In a typical Virtual Machine Monitor (VMM) there are several components, such as boot loader, virtual device drivers, virtio backend drivers and vhost drivers, that need to access the VM physical memory. The vm-memory rust crate provides a set of traits to decouple VM memory consumers from VM memory providers. 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. Users are advised to upgrade. There are no known workarounds for this issue.","state":0,"publishedAt":"2023-09-01T18:22:53.404+00:00","modifiedAt":"2025-02-13T17:08:47.589+00:00","affected":[{"ecosystem":"Vendor product","name":"vm-memory","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"rust-vmm\",\n                    \"product\": \"vm-memory\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 0.1.0, < 0.12.2\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L","score":2.5,"severity":"LOW"}],"references":["https://github.com/rust-vmm/vm-memory/security/advisories/GHSA-49hh-fprx-m68g","https://github.com/rust-vmm/vm-memory/commit/aff1dd4a5259f7deba56692840f7a2d9ca34c9c8","https://crates.io/crates/vm-memory/0.12.2","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XZGJL6BQLU4XCPQLLTW4GSSBTNQXB3TI/","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IPXRXD5VXBZHBGMUM77B52CJJMG7EJGI/","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SYM6CYW2DWRHRAVL2HYTQPXC3J2V77J4/"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2023-41051","license":"CVE Program Terms of Use","key":"cve-program:CVE-2023-41051","identifiers":["CVE-2023-41051"]},"retained":false,"historicalAffected":[]},{"revision":"518359f6343848b3a5502a67e14d3813","observedAt":"2026-11-15T00:32:22.421+00:00","statement":{"source":"euvd","id":"EUVD-2023-2414","aliases":["CVE-2023-41051","GHSA-49hh-fprx-m68g"],"title":"In a typical Virtual Machine Monitor (VMM) there are several components, such as boot loader, virtual device drivers, virtio backend drivers and vhost drivers, that need to access the VM physical memory. The vm-memory rust crate provides a …","description":"In a typical Virtual Machine Monitor (VMM) there are several components, such as boot loader, virtual device drivers, virtio backend drivers and vhost drivers, that need to access the VM physical memory. The vm-memory rust crate provides a set of traits to decouple VM memory consumers from VM memory providers. 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. Users are advised to upgrade. There are no known workarounds for this issue.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L","score":2.5,"severity":null}],"references":["https://github.com/rust-vmm/vm-memory/security/advisories/GHSA-49hh-fprx-m68g","https://github.com/rust-vmm/vm-memory/commit/aff1dd4a5259f7deba56692840f7a2d9ca34c9c8","https://crates.io/crates/vm-memory/0.12.2","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XZGJL6BQLU4XCPQLLTW4GSSBTNQXB3TI/","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IPXRXD5VXBZHBGMUM77B52CJJMG7EJGI/","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SYM6CYW2DWRHRAVL2HYTQPXC3J2V77J4/"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2023-2414","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Sep 1, 2023, 6:22:53 PM","dateUpdated":"Feb 13, 2025, 5:08:47 PM"},"relatedAdvisories":[{"id":"msrc_CVE-2023-41051","title":"Default functions in VolatileMemory trait lack bounds checks in vm-memory","vulnerabilityIds":["CVE-2023-41051"]}],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2023-2414","identifiers":["EUVD-2023-2414","CVE-2023-41051","GHSA-49hh-fprx-m68g"]},"retained":false,"historicalAffected":[]},{"revision":"7eafca12c3444a139c65a9b24a384589","observedAt":"2026-10-24T22:17:27.792+00:00","statement":{"source":"nvd","id":"CVE-2023-41051","aliases":[],"title":"In a typical Virtual Machine Monitor (VMM) there are several components, such as boot loader, virtual device drivers, virtio backend drivers and vhost drivers, that need to access the VM physical memory. The vm-memory rust crate provides a …","description":"In a typical Virtual Machine Monitor (VMM) there are several components, such as boot loader, virtual device drivers, virtio backend drivers and vhost drivers, that need to access the VM physical memory. The vm-memory rust crate provides a set of traits to decouple VM memory consumers from VM memory providers. 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. Users are advised to upgrade. There are no known workarounds for this issue.","state":0,"publishedAt":"2023-09-01T19:15:42.883+00:00","modifiedAt":"2026-06-17T06:20:18.557+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L","score":2.5,"severity":"LOW"},{"system":"CVSS 3.1 · nvd@nist.gov · Primary","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H","score":4.7,"severity":"MEDIUM"}],"references":["https://crates.io/crates/vm-memory/0.12.2","https://github.com/rust-vmm/vm-memory/commit/aff1dd4a5259f7deba56692840f7a2d9ca34c9c8","https://github.com/rust-vmm/vm-memory/security/advisories/GHSA-49hh-fprx-m68g","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IPXRXD5VXBZHBGMUM77B52CJJMG7EJGI/","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SYM6CYW2DWRHRAVL2HYTQPXC3J2V77J4/","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XZGJL6BQLU4XCPQLLTW4GSSBTNQXB3TI/"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2023-41051","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Modified","weaknesses":["CWE-125"],"productCriteria":["cpe:2.3:a:vm-memory_project:vm-memory:*:*:*:*:*:rust:*:*"],"sourceDates":{"published":"2023-09-01T19:15:42.883","lastModified":"2026-06-17T06:20:18.557"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2023-41051","identifiers":["CVE-2023-41051"]},"retained":false,"historicalAffected":[]},{"revision":"5b9191233b944ee4a8c5fbe61d432fd0","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"GHSA-49hh-fprx-m68g","aliases":["CVE-2023-41051","RUSTSEC-2023-0056"],"title":"Default functions in VolatileMemory trait lack bounds checks, potentially leading to out-of-bounds memory accesses","description":"### Impact\nAn 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.\n\n### Patches\nThe 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.\n\n### Workarounds\nNot Required\n\n### References\nhttps://github.com/rust-vmm/vm-memory/commit/aff1dd4a5259f7deba56692840f7a2d9ca34c9c8\nhttps://crates.io/crates/vm-memory/0.12.2","state":0,"publishedAt":"2023-09-04T16:35:37+00:00","modifiedAt":"2026-09-10T03:50:03.1372698+00:00","affected":[{"ecosystem":"crates.io","name":"vm-memory","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"0.12.2"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"LOW"}],"references":["https://github.com/rust-vmm/vm-memory/security/advisories/GHSA-49hh-fprx-m68g","https://nvd.nist.gov/vuln/detail/CVE-2023-41051","https://github.com/rust-vmm/vm-memory/issues/250","https://github.com/rust-vmm/vm-memory/commit/aff1dd4a5259f7deba56692840f7a2d9ca34c9c8","https://crates.io/crates/vm-memory/0.12.2","https://github.com/rust-vmm/vm-memory","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IPXRXD5VXBZHBGMUM77B52CJJMG7EJGI","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SYM6CYW2DWRHRAVL2HYTQPXC3J2V77J4","https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XZGJL6BQLU4XCPQLLTW4GSSBTNQXB3TI","https://rustsec.org/advisories/RUSTSEC-2023-0056.html"],"sourceUrl":"https://github.com/advisories/GHSA-49hh-fprx-m68g","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-49hh-fprx-m68g","identifiers":["GHSA-49hh-fprx-m68g","CVE-2023-41051","RUSTSEC-2023-0056"]},"retained":false,"historicalAffected":[]},{"revision":"45798dbbdf5a49f088cd74a967069b65","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"RUSTSEC-2023-0056","aliases":["CVE-2023-41051","GHSA-49hh-fprx-m68g"],"title":"Default functions in VolatileMemory trait lack bounds checks, potentially leading to out-of-bounds memory accesses","description":"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.\n\nThe 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.","state":0,"publishedAt":"2023-09-01T12:00:00+00:00","modifiedAt":"2023-11-08T04:13:24.18898+00:00","affected":[{"ecosystem":"crates.io","name":"vm-memory","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.0.0-0"},{"kind":"fixed","version":"0.12.2"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L","score":null,"severity":null}],"references":["https://crates.io/crates/vm-memory","https://rustsec.org/advisories/RUSTSEC-2023-0056.html","https://github.com/rust-vmm/vm-memory/issues/250","https://github.com/rust-vmm/vm-memory/commit/aff1dd4a5259f7deba56692840f7a2d9ca34c9c8"],"sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2023-0056","license":"OSV · upstream source license applies","key":"osv:RUSTSEC-2023-0056","identifiers":["RUSTSEC-2023-0056","CVE-2023-41051","GHSA-49hh-fprx-m68g"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-16T15:46:28.5867679+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-16T15:46:28.5867679+00:00","lastSuccessAt":"2026-11-16T15:46:28.7336518+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.7336528+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-6be044d0e08779dadd136f949a536de4047af96f5d7bceb7e190ecffbb8f18ca-12f82bfd2f0251f244474ead94aa147d6e6e5a295312f7bfcd9f3990dddcf44d","complete":true,"records":426048,"lastAttemptAt":"2026-11-16T15:44:51.0968416+00:00","lastSuccessAt":"2026-11-16T15:44:51.0015391+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:44:51.0968416+00:00","snapshotPublishedAt":"2026-11-16T15:30:52+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-b53a453bd21948638a37a0c1d9db90a8","complete":true,"records":13830,"lastAttemptAt":"2026-11-16T15:47:10.0420289+00:00","lastSuccessAt":"2026-11-16T15:47:10.038+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:47:10.038+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13883,"expectedIdentifiers":13883,"failedIdentifiers":0},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-16T15:46:28.5867679+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-16T15:46:28.5867679+00:00","lastSuccessAt":"2026-11-16T15:46:28.7348718+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.7348721+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-9aad64c357a84d2b95eb370a9099d8a7","complete":false,"records":13842,"lastAttemptAt":"2026-11-16T15:46:54.2697305+00:00","lastSuccessAt":"2026-11-16T15:46:54.266+00:00","error":"209 identifier lookups failed; latest failures include HttpError (HTTP 503). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-16T15:46:54.266+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13674,"expectedIdentifiers":13883,"failedIdentifiers":209},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-64eea06dbd27de8464d5dbce1b78cc794cc59e2d901516ae0d3ea76e624cdae0","complete":true,"records":9955,"lastAttemptAt":"2026-11-16T15:46:28.4519077+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.4519077+00:00","snapshotPublishedAt":"2026-11-14T13:17:57+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-16T15:44:51.2546448+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:44:51.2546448+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-6086d649bcb454cdf302d7d9275177bda73550e1b6e446b3520e9b6266d3582c","complete":true,"records":3148,"lastAttemptAt":"2026-11-16T15:46:28.5571571+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.5571571+00:00","snapshotPublishedAt":"2026-11-15T10:03:04+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-58b43c63da2e2d496e2f653c5bea97bd9deda68f62d1c3a4dc0212d13b04b5b2","complete":true,"records":232492,"lastAttemptAt":"2026-11-16T15:46:28.326888+00:00","lastSuccessAt":"2026-11-16T15:46:27.3875263+00:00","error":null,"lastVerifiedAt":"2026-11-16T15:46:28.326888+00:00","snapshotPublishedAt":"2026-11-16T15:33:39+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}