Skip to content
Fencer Intel
medium 5.8

CVE-2013-6456 json

The LXC driver (lxc/lxc_driver.c) in libvirt 1.0.1 through 1.2.1 allows local users to (1) delete arbitrary host devices via the virDomainD…

published 12y ago modified 4mo ago also EUVD-2013-6263

cvss
5.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 47%
public exploits
0
none known

Summary

The LXC driver (lxc/lxc_driver.c) in libvirt 1.0.1 through 1.2.1 allows local users to (1) delete arbitrary host devices via the virDomainDeviceDettach API and a symlink attack on /dev in the container; (2) create arbitrary nodes (mknod) via the virDomainDeviceAttach API and a symlink attack on /dev in the container; and cause a denial of service (shutdown or reboot host OS) via the (3) virDomainShutdown or (4) virDomainReboot API and a symlink attack on /dev/initctl in the container, related to "paths under /proc/$PID/root" and the virInitctlSetRunLevel function.

Patch / fix

  • libvirt Debian 14, Debian 13, Debian 12 1.2.3-1

debian advisories DEBIAN-CVE-2013-6456

  • libvirt openSUSE Tumbleweed 2.5.0-1.1

opensuse advisories openSUSE-SU-2024:10209-1

Is CVE-2013-6456 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-6456 updated cvss 6.2

libvirt: unsafe usage of paths under /proc/$PID/root

  • Red Hat Enterprise Linux 7 libvirt, libvirt-nss, libvirt-libs, libvirt-admin, libvirt-client, libvirt-daemon, +24 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 5 libvirt Red Hat Enterprise Linux 6 libvirt, libvirt-client, libvirt-python, libvirt-lock-sanlock Red Hat Storage 2 libvirt
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.8 AV:A/AC:M/Au:S/C:N/I:P/A:C

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.