First published: Tue Mar 18 2014(Updated: )
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: <a href="http://libvirt.org/git/?p=libvirt.git;a=commit;h=484cc321">http://libvirt.org/git/?p=libvirt.git;a=commit;h=484cc321</a> Acknowledgements: This issue was discovered by Marian Krcmarik of Red Hat.
Affected Software | Affected Version | How to fix |
---|---|---|
Libvirt |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1077620 is considered to be critical due to the potential for daemon crashes during migration.
To fix REDHAT-BUG-1077620, ensure you apply the latest patches provided by Red Hat for libvirt.
All versions of libvirt that contain the specific bug are affected, so checking the changelog and updates is essential.
Yes, unprivileged users can potentially exploit the vulnerability in REDHAT-BUG-1077620 during migration operations.
The crash in REDHAT-BUG-1077620 occurs when domblkstat is called simultaneously with qemuMonitorGetSpiceMigrationStatus during migration.