CVE-2013-4292 json
libvirt 1.1.0 and 1.1.1 allows local users to cause a denial of service (memory consumption) via a large number of domain migrate parameter…
published 2013-09-30 13 y ago modified 2026-06-16 4 mo ago also EUVD-2013-4188
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
libvirt 1.1.0 and 1.1.1 allows local users to cause a denial of service (memory consumption) via a large number of domain migrate parameters in certain RPC calls in (1) daemon/remote.c and (2) remote/remote_driver.c.
Patch / fix
- libvirt Debian 14, Debian 13, Debian 12 1.1.2~rc2-1
debian advisories DEBIAN-CVE-2013-4292
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-4292 updated cvss 4.3
libvirt: unbounded RPC arrays in remote protocol
-
Red Hat Enterprise Linux 5 libvirt Red Hat Enterprise Linux 6 libvirt, libvirt-client, libvirt-python, libvirt-lock-sanlock Red Hat Enterprise Linux 7 libvirt, libvirt-nss, libvirt-libs, libvirt-admin, libvirt-client, libvirt-daemon, +24 morenot 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.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
security.gentoo.org
/glsa/glsa-201412-04.xml
vendor-advisory
- libvirt.org /news.html
-
secunia.com
/advisories/60895
third-party-advisory
-
mail-archive.com
/libvir-list%40redhat.com/msg83332.html
mailing-list
Sources
- CVE List CVE-2013-4292
- NVD CVE-2013-4292
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.