First published: Fri Jul 19 2013(Updated: )
A part of the returned monitor response was freed twice and caused crashes of the daemon when using guest agent cpu count retrieval. A remote user able to issue commands to libvirt daemon could use this flaw to crash libvirtd or, potentially, escalate their privilages to that of libvirtd process. References: <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - Crash of libvirtd without guest agent configuration" href="show_bug.cgi?id=984821">https://bugzilla.redhat.com/show_bug.cgi?id=984821</a> <a href="https://www.redhat.com/archives/libvir-list/2013-July/msg01035.html">https://www.redhat.com/archives/libvir-list/2013-July/msg01035.html</a> Acknowledgements: This issue was discovered by Petr Krempa of Red Hat.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Libvirt-daemon-driver-storage-iscsi-direct | =1.0.6 | |
Red Hat Libvirt-daemon-driver-storage-iscsi-direct | =1.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2013-4153 is considered high due to its potential for privilege escalation and crashing the daemon.
To fix CVE-2013-4153, you should upgrade your libvirt installation to a version that addresses this vulnerability, such as 1.0.7 or later.
CVE-2013-4153 affects users of Red Hat Libvirt versions 1.0.6 and 1.1.0.
The exploit vector for CVE-2013-4153 is a remote user with the capability to issue commands to the libvirt daemon.
The consequences of CVE-2013-4153 may include crashing the libvirtd process and potential privilege escalation for an attacker.