vmm-sys-util
Activity
- Latest release
- 1y ago
- Total releases
- 22
- Cadence
- ~2 months
- Last 12 months
- 0
Details
- License
- BSD-3-Clause
- First release
- Oct 08, 2019
| Version | Released | |
|---|---|---|
0.15.0
unknown
|
0.15.0
unknown
Dependencies (6)
|
|
0.14.0
unknown
|
0.14.0
unknown
Dependencies (6)
|
|
0.13.0
unknown
|
0.13.0
unknown
Dependencies (6)
|
|
0.12.1
unknown
|
0.12.1
unknown
Dependencies (6)
|
|
0.12.0
unknown
yanked
|
0.12.0
unknown
yanked
Dependencies (6)
|
|
0.11.2
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.11.2
unknown
Dependencies (5)
|
|
0.11.1
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.11.1
unknown
Dependencies (5)
|
|
0.11.0
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.11.0
unknown
Dependencies (5)
|
|
0.10.0
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.10.0
unknown
Dependencies (5)
|
|
0.9.0
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.9.0
unknown
Dependencies (5)
|
|
0.8.0
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.8.0
unknown
Dependencies (5)
|
|
0.7.0
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.7.0
unknown
Dependencies (5)
|
|
0.6.1
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.6.1
unknown
Dependencies (5)
|
|
0.6.0
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.6.0
unknown
Dependencies (5)
|
|
0.5.0
unknown
1 CVE
CVE-2023-50711
GHSA-875g-mfp6-g7f9
RUSTSEC-2024-0002
Jan 02, 2024
`serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
5.7
/ 10
Medium
Local
Low
None
None
Changed
None
Low
Low
ImpactAn issue was discovered in the FamStructWrapper::deserialize implementation provided by the crate for vmm_sys_util::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 PatchesThe 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. Fixed in
0.12.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.5.0
unknown
Dependencies (5)
|
|
0.4.0
unknown
|
0.4.0
unknown
Dependencies (1)
|
|
0.3.1
unknown
|
0.3.1
unknown
Dependencies (1)
|
|
0.3.0
unknown
|
0.3.0
unknown
Dependencies (1)
|
|
0.2.1
unknown
|
0.2.1
unknown
Dependencies (1)
|
|
0.2.0
unknown
|
0.2.0
unknown
Dependencies (1)
|
|
0.1.1
unknown
|
0.1.1
unknown
Dependencies (1)
|
|
0.1.0
unknown
yanked
|
0.1.0
unknown
yanked
Dependencies (1)
|