CVE-2013-7336: The qemuMigrationWaitForSpice function in qemu/qemu_migration.c in libvirt before 1.1.3 does not properly enter a monitor when performing…
Noroxi assessment
Priority: Monitor (action score 7/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- Fixed version: libvirt (Debian:12) 1.1.4-1; libvirt (Red Hat:enterprise_linux:6::client) 0:0.10.2-29.el6; libvirt-client (Red Hat:enterprise_linux:6::client) 0:0.10.2-29.el6.
Low priority for now. Upgrade to libvirt (Debian:12) 1.1.4-1; libvirt (Red Hat:enterprise_linux:6::client) 0:0.10.2-29.el6; libvirt-client (Red Hat:enterprise_linux:6::client) 0:0.10.2-29.el6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The qemuMigrationWaitForSpice function in qemu/qemu_migration.c in libvirt before 1.1.3 does not properly enter a monitor when performing seamless SPICE migration, which allows local users to cause a denial of service (NULL pointer dereference and libvirtd crash) by causing domblkstat to be called at the same time as the qemuMonitorGetSpiceMigrationStatus function.
- Published
- May 7, 2014
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- —
Report tools
Action score
7
Low priority for now.
- CVSS
- 7 / 40 · 1.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensuse opensuse13.1
- redhat libvirtup to 1.1.2 inclusive
- redhat libvirt1.0.0
- redhat libvirt1.0.1
- redhat libvirt1.0.2
- redhat libvirt1.0.3
- redhat libvirt1.0.4
- redhat libvirt1.0.5
+9 more rows
- redhat libvirt1.0.5.1
- redhat libvirt1.0.5.2
- redhat libvirt1.0.5.3
- redhat libvirt1.0.5.4
- redhat libvirt1.0.5.5
- redhat libvirt1.0.5.6
- redhat libvirt1.0.6
- redhat libvirt1.1.0
- redhat libvirt1.1.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libvirt | before 1.1.4-1 | 1.1.4-1 |
| Red Hat:enterprise_linux:6::client | libvirt | before 0:0.10.2-29.el6 | 0:0.10.2-29.el6 |
| Red Hat:enterprise_linux:6::client | libvirt-client | before 0:0.10.2-29.el6 | 0:0.10.2-29.el6 |
| Red Hat:enterprise_linux:6::client | libvirt-debuginfo | before 0:0.10.2-29.el6 | 0:0.10.2-29.el6 |
| Red Hat:enterprise_linux:6::client | libvirt-devel | before 0:0.10.2-29.el6 | 0:0.10.2-29.el6 |
| Red Hat:enterprise_linux:6::client | libvirt-lock-sanlock | before 0:0.10.2-29.el6 | 0:0.10.2-29.el6 |
| Red Hat:enterprise_linux:6::client | libvirt-python | before 0:0.10.2-29.el6 | 0:0.10.2-29.el6 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-5008libvirt before 2.0.0 improperly disables password checking when the password on a VNC server is set to an empty string, which allows remote…40Plan
- CVE-2020-14339A flaw was found in libvirt, where it leaked a file descriptor for `/dev/mapper/control` into the QEMU process.35Monitor
- CVE-2019-10132A vulnerability was found in libvirt >= 4.1.0 in the virtlockd-admin.socket and virtlogd-admin.socket systemd units.35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2014-1447Jan 24, 2014 · Race condition in the virNetServerClientStartKeepAlive function in libvirt before 1.2.1 allows remote attackers to cause a denial of…14Monitor
- ← EarlierCVE-2013-6456Apr 15, 2014 · 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…23Monitor
- Later →CVE-2014-0179Aug 3, 2014 · libvirt 0.7.5 through 1.2.x before 1.2.5 allows local users to cause a denial of service (read block and hang) via a crafted XML document…7Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libvirt | 1.1.4-1 · Debian:12 | Package registry (OSV) |
| red hat:libvirt | 0:0.10.2-29.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-client | 0:0.10.2-29.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-debuginfo | 0:0.10.2-29.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-devel | 0:0.10.2-29.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-lock-sanlock | 0:0.10.2-29.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-python | 0:0.10.2-29.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
—
CVSS vector
AV:L/AC:M/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.