Description of the problem: Domblkstat is possible even with read-only connection, so whenever migration with spice is done and domblkstat gets called at the same time as qemuMonitorGetSpiceMigrationStatus(), there is certain possibility that the daemon crashes. An unprivileged user able to issue commands to running libvirtd could use this flaw to crash libvirtd and prevent more privileged clients from working correctly. Upstream fix: http://libvirt.org/git/?p=libvirt.git;a=commit;h=484cc321 Acknowledgements: This issue was discovered by Marian Krcmarik of Red Hat.
Statement: Not vulnerable. This issue did not affect the versions of libvirt package as shipped with Red Hat Enterprise Linux 5 and 6 (since http://rhn.redhat.com/errata/RHBA-2013-1581.html, Red Hat Enterprise Linux 6.5 GA).
(In reply to Petr Matousek from comment #1) > Statement: > > Not vulnerable. > > This issue did not affect the versions of libvirt package as shipped with > Red Hat Enterprise Linux 5 and 6. It turns out that I missed that the vulnerability had been backported to RHEL 6 as a result of bug 920205 (libvirt-0.10.2-20.el6); it was fixed for libvirt-0.10.2-27.el6.
(In reply to Eric Blake from comment #2) > It turns out that I missed that the vulnerability had been backported to > RHEL 6 as a result of bug 920205 (libvirt-0.10.2-20.el6); it was fixed for > libvirt-0.10.2-27.el6. Thanks, Eric. I've adjusted the statement.