Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1141131 - (CVE-2014-3633) CVE-2014-3633 libvirt: qemu: out-of-bounds read access in qemuDomainGetBlockIoTune() due to invalid index
CVE-2014-3633 libvirt: qemu: out-of-bounds read access in qemuDomainGetBlockI...
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20140917,repor...
: Security
Depends On: 1140724 1141134 1143891 1160278 1160823
Blocks: 1141096 1143903 1160286
  Show dependency treegraph
 
Reported: 2014-09-12 05:37 EDT by Petr Matousek
Modified: 2015-06-01 08:49 EDT (History)
18 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
An out-of-bounds read flaw was found in the way libvirt's qemuDomainGetBlockIoTune() function looked up the disk index in a non-persistent (live) disk configuration while a persistent disk configuration was being indexed. A remote attacker able to establish a read-only connection to libvirtd could use this flaw to crash libvirtd or, potentially, leak memory from the libvirtd process.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-11-18 16:49:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:1352 normal SHIPPED_LIVE Moderate: libvirt security and bug fix update 2014-10-01 19:11:16 EDT
Red Hat Product Errata RHSA-2014:1873 normal SHIPPED_LIVE Moderate: libvirt security and bug fix update 2014-11-18 18:08:55 EST

  None (edit)
Description Petr Matousek 2014-09-12 05:37:10 EDT
It was found that when a disk is attached to a disk "live" (thus not
written into the persistent configuration) and then the statistics for
the disks are requested from the persistent configuration, index to
the array is determined from the live configuration but used in the
persistent.

A remote attacker able to establish a read-only connection to libvirtd
could use this flaw to crash libvirtd or, potentially, leak memory from
the libvirtd process.

Acknowledgements:

This issue was discovered by Luyao Huang of Red Hat.
Comment 1 Petr Matousek 2014-09-12 05:38:43 EDT
Statement:

This issue does not affect the versions of libvirt packages as shipped with
Red Hat Enterprise Linux 5.

This issue does affect the versions of libvirt packages as shipped with Red Hat
Enterprise Linux 6 and 7. Future updates may address this issue in the
respective Red Hat Enterprise Linux releases.
Comment 5 Martin Prpič 2014-09-30 11:37:28 EDT
IssueDescription:

An out-of-bounds read flaw was found in the way libvirt's qemuDomainGetBlockIoTune() function looked up the disk index in a non-persistent (live) disk configuration while a persistent disk configuration was being indexed. A remote attacker able to establish a read-only connection to libvirtd could use this flaw to crash libvirtd or, potentially, leak memory from the libvirtd process.
Comment 6 errata-xmlrpc 2014-10-01 15:11:33 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2014:1352 https://rhn.redhat.com/errata/RHSA-2014-1352.html
Comment 8 Petr Matousek 2014-11-05 12:32:40 EST
Created libvirt tracking bugs for this issue:

Affects: fedora-all [bug 1160823]
Comment 9 errata-xmlrpc 2014-11-18 13:09:11 EST
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2014:1873 https://rhn.redhat.com/errata/RHSA-2014-1873.html
Comment 10 Fedora Update System 2014-11-22 07:37:10 EST
libvirt-1.1.3.8-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.