Moderate CentOS libvirt Update


libvirt-0.10.2-29.el6_5.3.i686.rpm, libvirt-0.10.2-29.el6_5.3.src.rpm, libvirt-0.10.2-29.el6_5.3.x86_64.rpm, libvirt-client-0.10.2-29.el6_5.3.i686.rpm, libvirt-client-0.10.2-29.el6_5.3.x86_64.rpm, libvirt-devel-0.10.2-29.el6_5.3.i686.rpm, libvirt-devel-0.10.2-29.el6_5.3.x86_64.rpm, libvirt-lock-sanlock-0.10.2-29.el6_5.3.x86_64.rpm, libvirt-python-0.10.2-29.el6_5.3.i686.rpm, libvirt-python-0.10.2-29.el6_5.3.x86_64.rpm,
2018-01-18 11:06
2017-07-27 19:06
2017-04-01 19:07
2017-01-05 20:11


Updated libvirt packages that fix two security issues and one bug are now
available for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having moderate
security impact. Common Vulnerability Scoring System (CVSS) base scores,
which give detailed severity ratings, are available for each vulnerability
from the CVE links in the References section.

The libvirt library is a C API for managing and interacting with the
virtualization capabilities of Linux and other operating systems.
In addition, libvirt provides tools for remote management of
virtualized systems.

A use-after-free flaw was found in the way several libvirt block APIs
handled domain jobs. A remote attacker able to establish a read-only
connection to libvirtd could use this flaw to crash libvirtd or,
potentially, execute arbitrary code with the privileges of the libvirtd
process (usually root). (CVE-2013-6458)

A race condition was found in the way libvirtd handled keepalive
initialization requests when the connection was closed prior to
establishing connection credentials. An attacker able to establish a
read-only connection to libvirtd could use this flaw to crash libvirtd,
resulting in a denial of service. (CVE-2014-1447)

This update also fixes the following bug:

* A race condition was possible between a thread starting a virtual machine
with a guest agent configured (regular start-up or while migrating) and a
thread that was killing the VM process (or the process crashing). The race
could cause the monitor object to be freed by the thread that killed the VM
process, which was later accessed by the thread that was attempting to
start the VM, resulting in a crash. This issue was fixed by checking the
state of the VM after the attempted connection to the guest agent; if the
VM in the meantime exited, no other operations are attempted. (BZ#1055578)

All libvirt users are advised to upgrade to these updated packages, which
contain backported patches to correct these issues. After installing the
updated packages, libvirtd will be restarted automatically.
Please see

Am I vulnerable?

The constraints below list the versions that this vulnerability is patched in, and versions that are unaffected. If a patch is ready but unrealeased, then it is pending.

Or, you can just let us figure it out for you! Appcanary continously monitor your installed packages, and tell you if any of them are vulnerable.

Sign up for monitoring

Affected package information

Release Package Patched in
6 libvirt libvirt-0.10.2-29.el6_5.3.i686.rpm
libvirt libvirt-0.10.2-29.el6_5.3.src.rpm
libvirt libvirt-0.10.2-29.el6_5.3.x86_64.rpm
libvirt-client libvirt-client-0.10.2-29.el6_5.3.i686.rpm
libvirt-client libvirt-client-0.10.2-29.el6_5.3.x86_64.rpm
libvirt-devel libvirt-devel-0.10.2-29.el6_5.3.i686.rpm
libvirt-devel libvirt-devel-0.10.2-29.el6_5.3.x86_64.rpm
libvirt-lock-sanlock libvirt-lock-sanlock-0.10.2-29.el6_5.3.x86_64.rpm
libvirt-python libvirt-python-0.10.2-29.el6_5.3.i686.rpm
libvirt-python libvirt-python-0.10.2-29.el6_5.3.x86_64.rpm