410
VMScore

CVE-2021-3713

Published: 25/08/2021 Updated: 25/10/2022
CVSS v2 Base Score: 4.6 | Impact Score: 6.4 | Exploitability Score: 3.9
CVSS v3 Base Score: 7.4 | Impact Score: 6 | Exploitability Score: 0.7
VMScore: 410
Vector: AV:L/AC:L/Au:N/C:P/I:P/A:P

Vulnerability Summary

An out-of-bounds write flaw was found in the UAS (USB Attached SCSI) device emulation of QEMU in versions before 6.2.0-rc0. The device uses the guest supplied stream number unchecked, which can lead to out-of-bounds access to the UASDevice->data3 and UASDevice->status3 fields. A malicious guest user could use this flaw to crash QEMU or potentially achieve code execution with the privileges of the QEMU process on the host.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

qemu qemu

debian debian linux 9.0

debian debian linux 10.0

debian debian linux 11.0

Vendor Advisories

Debian Bug report logs - #992727 qemu: CVE-2021-3713 Package: src:qemu; Maintainer for src:qemu is Debian QEMU Team <pkg-qemu-devel@listsaliothdebianorg>; Reported by: Salvatore Bonaccorso <carnil@debianorg> Date: Sun, 22 Aug 2021 18:45:04 UTC Severity: important Tags: security, upstream Found in version qemu/1: ...
Several security issues were fixed in QEMU ...
Multiple security issues were discovered in QEMU, a fast processor emulator, which could result in denial of service or the the execution of arbitrary code For the stable distribution (bullseye), these problems have been fixed in version 1:52+dfsg-11+deb11u1 We recommend that you upgrade your qemu packages For the detailed security status of qe ...
An out-of-bounds write flaw was found in the UAS (USB Attached SCSI) device emulation of QEMU The device uses the guest supplied stream number unchecked, which can lead to out-of-bounds access to the UASDevice->data3 and UASDevice->status3 fields A malicious guest user could use this flaw to crash QEMU or potentially achieve code ex ...
An out-of-bounds write issue was found in the UAS (USB Attached SCSI) device emulation of QEMU It occurs due to missing sanity checks in the usb_uas_handle_data() function in hw/usb/dev-uasc In particular, the device uses the guest-supplied stream number unchecked, which can lead to guest-triggered out-of-bounds access to the UASDevice->data3 ...