CVE Vulnerabilities

CVE-2015-8817

Out-of-bounds Read

Published: Dec 29, 2016 | Modified: Feb 12, 2023
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
4 LOW
AV:A/AC:H/Au:S/C:P/I:P/A:P
RedHat/V3
Ubuntu
LOW

QEMU (aka Quick Emulator) built to use address_space_translate to map an address to a MemoryRegionSection is vulnerable to an OOB r/w access issue. It could occur while doing pci_dma_read/write calls. Affects QEMU versions >= 1.6.0 and <= 2.3.1. A privileged user inside guest could use this flaw to crash the guest instance resulting in DoS.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Qemu Qemu 1.6.0 (including) 1.6.0 (including)
Qemu Qemu 1.6.0-rc1 (including) 1.6.0-rc1 (including)
Qemu Qemu 1.6.0-rc2 (including) 1.6.0-rc2 (including)
Qemu Qemu 1.6.0-rc3 (including) 1.6.0-rc3 (including)
Qemu Qemu 1.6.1 (including) 1.6.1 (including)
Qemu Qemu 1.6.2 (including) 1.6.2 (including)
Qemu Qemu 1.7.1 (including) 1.7.1 (including)
Qemu Qemu 2.0.0 (including) 2.0.0 (including)
Qemu Qemu 2.0.0-rc0 (including) 2.0.0-rc0 (including)
Qemu Qemu 2.0.0-rc1 (including) 2.0.0-rc1 (including)
Qemu Qemu 2.0.0-rc2 (including) 2.0.0-rc2 (including)
Qemu Qemu 2.0.0-rc3 (including) 2.0.0-rc3 (including)
Qemu Qemu 2.0.2 (including) 2.0.2 (including)
Qemu Qemu 2.1.0 (including) 2.1.0 (including)
Qemu Qemu 2.1.0-rc0 (including) 2.1.0-rc0 (including)
Qemu Qemu 2.1.0-rc1 (including) 2.1.0-rc1 (including)
Qemu Qemu 2.1.0-rc2 (including) 2.1.0-rc2 (including)
Qemu Qemu 2.1.0-rc3 (including) 2.1.0-rc3 (including)
Qemu Qemu 2.1.0-rc5 (including) 2.1.0-rc5 (including)
Qemu Qemu 2.1.1 (including) 2.1.1 (including)
Qemu Qemu 2.1.2 (including) 2.1.2 (including)
Qemu Qemu 2.1.3 (including) 2.1.3 (including)
Qemu Qemu 2.2.0 (including) 2.2.0 (including)
Qemu Qemu 2.2.1 (including) 2.2.1 (including)
Qemu Qemu 2.3.0 (including) 2.3.0 (including)
Qemu Qemu 2.3.1 (including) 2.3.1 (including)
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7 RedHat qemu-kvm-rhev-10:2.6.0-27.el7 *
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7 RedHat qemu-kvm-rhev-10:2.6.0-27.el7 *
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7 RedHat qemu-kvm-rhev-10:2.6.0-27.el7 *
Red Hat OpenStack Platform 8.0 (Liberty) RedHat qemu-kvm-rhev-10:2.6.0-27.el7 *
Red Hat OpenStack Platform 9.0 (Mitaka) RedHat qemu-kvm-rhev-10:2.6.0-27.el7 *
Qemu Ubuntu esm-infra-legacy/trusty *
Qemu Ubuntu trusty *
Qemu Ubuntu trusty/esm *
Qemu Ubuntu wily *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References