SCIENTIFIC-LINUX-ERRATA Archives

September 2013

SCIENTIFIC-LINUX-ERRATA@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Pat Riehecky <[log in to unmask]>
Reply To:
Date:
Thu, 19 Sep 2013 19:26:15 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (67 lines)
Synopsis:          Important: libvirt security and bug fix update
Advisory ID:       SLSA-2013:1272-1
Issue Date:        2013-09-19
CVE Numbers:       CVE-2013-4311
                   CVE-2013-4296
--

libvirt invokes the PolicyKit pkcheck utility to handle authorization. A
race condition was found in the way libvirt used this utility, allowing a
local user to bypass intended PolicyKit authorizations or execute
arbitrary commands with root privileges. (CVE-2013-4311)

Note: With this update, libvirt has been rebuilt to communicate with
PolicyKit via a different API that is not vulnerable to the race
condition. The polkit SLSA-2013:1270 advisory must also be installed to
fix the CVE-2013-4311 issue.

An invalid free flaw was found in libvirtd's
remoteDispatchDomainMemoryStats function. An attacker able to establish a
read-only connection to libvirtd could use this flaw to crash libvirtd.
(CVE-2013-4296)

This update also fixes the following bugs:

* Prior to this update, the libvirtd daemon leaked memory in the
virCgroupMoveTask() function. A fix has been provided which prevents
libvirtd from incorrect management of memory allocations.

* Previously, the libvirtd daemon was accessing one byte before the array
in the virCgroupGetValueStr() function. This bug has been fixed and
libvirtd now stays within the array bounds.

* When migrating, libvirtd leaked the migration URI (Uniform Resource
Identifier) on destination. A patch has been provided to fix this bug and
the migration URI is now freed correctly.

* Updating a network interface using virDomainUpdateDeviceFlags API failed
when a boot order was set for that interface. The update failed even if
the boot order was set in the provided device XML. The
virDomainUpdateDeviceFlags API has been fixed to correctly parse the boot
order specification from the provided device XML and updating network
interfaces with boot orders now works as expected.

After installing the updated packages, libvirtd will be restarted
automatically.
--

SL6
  x86_64
    libvirt-0.10.2-18.el6_4.14.x86_64.rpm
    libvirt-client-0.10.2-18.el6_4.14.i686.rpm
    libvirt-client-0.10.2-18.el6_4.14.x86_64.rpm
    libvirt-debuginfo-0.10.2-18.el6_4.14.i686.rpm
    libvirt-debuginfo-0.10.2-18.el6_4.14.x86_64.rpm
    libvirt-python-0.10.2-18.el6_4.14.x86_64.rpm
    libvirt-devel-0.10.2-18.el6_4.14.i686.rpm
    libvirt-devel-0.10.2-18.el6_4.14.x86_64.rpm
    libvirt-lock-sanlock-0.10.2-18.el6_4.14.x86_64.rpm
  i386
    libvirt-0.10.2-18.el6_4.14.i686.rpm
    libvirt-client-0.10.2-18.el6_4.14.i686.rpm
    libvirt-debuginfo-0.10.2-18.el6_4.14.i686.rpm
    libvirt-python-0.10.2-18.el6_4.14.i686.rpm
    libvirt-devel-0.10.2-18.el6_4.14.i686.rpm

- Scientific Linux Development Team

ATOM RSS1 RSS2