Skip to content

Versionize::deserialize implementation for FamStructWrapper<T> is lacking bound checks, potentially leading to out of bounds memory accesses

Moderate severity GitHub Reviewed Published Mar 24, 2023 in firecracker-microvm/versionize • Updated Mar 27, 2023

Package

cargo versionize (Rust)

Affected versions

>= 0.1.1, < 0.1.10

Patched versions

0.1.10

Description

Impact

An issue was discovered in the Versionize::deserialize implementation provided by the versionize crate for vmm_sys_util::fam::FamStructWrapper, which can lead to out of bounds memory accesses.

Patches

The impact started with version 0.1.1. The issue was corrected in version 0.1.10 by inserting a check that verifies, for any deserialized header, the lengths of compared flexible arrays are equal and aborting deserialization otherwise.

Workarounds

-

References

References

@roypat roypat published to firecracker-microvm/versionize Mar 24, 2023
Published by the National Vulnerability Database Mar 24, 2023
Published to the GitHub Advisory Database Mar 24, 2023
Reviewed Mar 24, 2023
Last updated Mar 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L

EPSS score

0.112%
(46th percentile)

Weaknesses

CVE ID

CVE-2023-28448

GHSA ID

GHSA-8vxc-r5wp-vgvc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.