CVE-2013-6457: Medium severity redhat libvirt vulnerability

Published Jan 5, 2014
·
Updated

An invalid free flaw in the libxl driver in libvirt resulted in libvirt crashing if "virsh numatune" was run on an inactive domain. It may be possible, but unlikely, for an attacker to leverage this flaw for arbitrary code execution.

This issue affects the version of libvirt in Fedora 20. It does not affect the versions of libvirt in Red Hat Enterprise Linux 5 and 6 as those versions do not use libxl.

Other sources

The libxlDomainGetNumaParameters function in the libxl driver (libxl/libxldriver.c) in libvirt before 1.2.1 does not properly initialize the nodemap, which allows local users to cause a denial of service (invalid free operation and crash) or possibly execute arbitrary code via an inactive domain to the virsh numatune command.

MITRE

Affected Software

110 affected components
redhat libvirt<=1.2.0
redhat libvirt=0.0.1
redhat libvirt=0.0.2
redhat libvirt=0.0.3
redhat libvirt=0.0.4
redhat libvirt=0.0.5
redhat libvirt=0.0.6
redhat libvirt=0.1.0
redhat libvirt=0.1.1
redhat libvirt=0.1.3
redhat libvirt=0.1.4
redhat libvirt=0.1.5
redhat libvirt=0.1.6
redhat libvirt=0.1.7
redhat libvirt=0.1.8
redhat libvirt=0.1.9
redhat libvirt=0.2.0
redhat libvirt=0.2.1
redhat libvirt=0.2.2
redhat libvirt=0.2.3
redhat libvirt=0.3.0
redhat libvirt=0.3.1
redhat libvirt=0.3.2
redhat libvirt=0.3.3
redhat libvirt=0.4.0
redhat libvirt=0.4.1
redhat libvirt=0.4.2
redhat libvirt=0.4.3
redhat libvirt=0.4.4
redhat libvirt=0.4.5
redhat libvirt=0.4.6
redhat libvirt=0.5.0
redhat libvirt=0.5.1
redhat libvirt=0.6.0
redhat libvirt=0.6.1
redhat libvirt=0.6.2
redhat libvirt=0.6.3
redhat libvirt=0.6.4
redhat libvirt=0.6.5
redhat libvirt=0.7.0
redhat libvirt=0.7.1
redhat libvirt=0.7.2
redhat libvirt=0.7.3
redhat libvirt=0.7.4
redhat libvirt=0.7.5
redhat libvirt=0.7.6
redhat libvirt=0.7.7
redhat libvirt=0.8.0
redhat libvirt=0.8.1
redhat libvirt=0.8.2
redhat libvirt=0.8.3
redhat libvirt=0.8.4
redhat libvirt=0.8.5
redhat libvirt=0.8.6
redhat libvirt=0.8.7
redhat libvirt=0.8.8
redhat libvirt=0.9.0
redhat libvirt=0.9.1
redhat libvirt=0.9.2
redhat libvirt=0.9.3
redhat libvirt=0.9.4
redhat libvirt=0.9.5
redhat libvirt=0.9.6
redhat libvirt=0.9.6.1
redhat libvirt=0.9.6.2
redhat libvirt=0.9.6.3
redhat libvirt=0.9.7
redhat libvirt=0.9.8
redhat libvirt=0.9.9
redhat libvirt=0.9.10
redhat libvirt=0.9.11
redhat libvirt=0.9.11.1
redhat libvirt=0.9.11.2
redhat libvirt=0.9.11.3
redhat libvirt=0.9.11.4
redhat libvirt=0.9.11.5
redhat libvirt=0.9.11.6
redhat libvirt=0.9.11.7
redhat libvirt=0.9.11.8
redhat libvirt=0.9.12
redhat libvirt=0.9.13
redhat libvirt=0.10.0
redhat libvirt=0.10.1
redhat libvirt=0.10.2
redhat libvirt=0.10.2.1
redhat libvirt=0.10.2.2
redhat libvirt=0.10.2.3
redhat libvirt=0.10.2.4
redhat libvirt=0.10.2.5
redhat libvirt=0.10.2.6
redhat libvirt=0.10.2.7
redhat libvirt=0.10.2.8
redhat libvirt=1.0.0
redhat libvirt=1.0.1
redhat libvirt=1.0.2
redhat libvirt=1.0.3
redhat libvirt=1.0.4
redhat libvirt=1.0.5
redhat libvirt=1.0.5.1
redhat libvirt=1.0.5.2
redhat libvirt=1.0.5.3
redhat libvirt=1.0.5.4
redhat libvirt=1.0.5.5
redhat libvirt=1.0.5.6
redhat libvirt=1.0.6
redhat libvirt=1.1.0
redhat libvirt=1.1.1
redhat libvirt=1.1.2
redhat libvirt=1.1.3
redhat libvirt=1.1.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade libvirt/libxl driver (libxl) to a version that resolves this vulnerability.

    Fixed in 1.2.1
  2. Compensating control

    Do not run "virsh numatune" against inactive domains until the libvirt fix is applied, since the crash is triggered by running this command on an inactive domain.

Event History

Jan 5, 2014
Data Sourced
via Red Hat·11:54 PM
DescriptionSeverityAffected Software
Jan 24, 2014
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Data Sourced
via NVD·06:55 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2013-6457?

CVE-2013-6457 has a moderate severity level due to the potential for application crashes and the unlikely possibility of arbitrary code execution.

2

How do I fix CVE-2013-6457?

To fix CVE-2013-6457, update to a patched version of libvirt that addresses the invalid free flaw.

3

Which versions of libvirt are affected by CVE-2013-6457?

CVE-2013-6457 affects versions of libvirt up to and including 1.2.0.

4

What types of systems are impacted by CVE-2013-6457?

Systems running vulnerable versions of libvirt, particularly those deployed on Fedora 20 and older versions, are impacted by CVE-2013-6457.

5

Are there known exploits for CVE-2013-6457?

There are no publicly available exploits for CVE-2013-6457, making the risk of exploitation relatively low for most users.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203