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.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Libvirt |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-986383 is considered to be high due to the potential for crashes and privilege escalation.
To fix REDHAT-BUG-986383, users should apply the latest security patches provided by Red Hat for the libvirt package.
Users running the affected versions of Red Hat libvirt are at risk of experiencing crashes or privilege escalation due to REDHAT-BUG-986383.
The potential impacts of REDHAT-BUG-986383 include system crashes of the libvirt daemon and possible unauthorized privilege escalation.
Currently, there are no specific workarounds for REDHAT-BUG-986383 other than applying the recommended patches.