Out-of-bounds Read Affecting libvirt-daemon-driver-storage package, versions <0:8.0.0-10.module+el8.7.0+1084+97b81f61


Severity

Recommended
low

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.05% (16th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ROCKY8-LIBVIRTDAEMONDRIVERSTORAGE-3272211
  • published5 Jan 2023
  • disclosed18 Feb 2022

Introduced: 18 Feb 2022

CVE-2022-23645  (opens in a new tab)
CWE-125  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:8 libvirt-daemon-driver-storage to version 0:8.0.0-10.module+el8.7.0+1084+97b81f61 or higher.
This issue was patched in RLSA-2022:7472.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libvirt-daemon-driver-storage package and not the libvirt-daemon-driver-storage package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:8 relevant fixed versions and status.

swtpm is a libtpms-based TPM emulator with socket, character device, and Linux CUSE interface. Versions prior to 0.5.3, 0.6.2, and 0.7.1 are vulnerable to out-of-bounds read. A specially crafted header of swtpm's state, where the blobheader's hdrsize indicator has an invalid value, may cause an out-of-bounds access when the byte array representing the state of the TPM is accessed. This will likely crash swtpm or prevent it from starting since the state cannot be understood. Users should upgrade to swtpm v0.5.3, v0.6.2, or v0.7.1 to receive a patch. There are currently no known workarounds.

CVSS Scores

version 3.1