CVE-2013-4151: Code Injection
Published Nov 4, 2014
·Updated
The virtioload function in virtio/virtio.c in QEMU 1.x before 1.7.2 allows remote attackers to execute arbitrary code via a crafted savevm image, which triggers an out-of-bounds write.
Affected Software
27 affected components
Qemu Qemu=1.0
Qemu Qemu=1.0-rc1
Qemu Qemu=1.0-rc2
Qemu Qemu=1.0-rc3
Qemu Qemu=1.0-rc4
Qemu Qemu=1.0.1
Qemu Qemu=1.1
Qemu Qemu=1.1-rc1
Qemu Qemu=1.1-rc2
Qemu Qemu=1.1-rc3
Qemu Qemu=1.1-rc4
Qemu Qemu=1.4.1
Qemu Qemu=1.4.2
Qemu Qemu=1.5.0
Qemu Qemu=1.5.0-rc1
Qemu Qemu=1.5.0-rc2
Qemu Qemu=1.5.0-rc3
Qemu Qemu=1.5.1
Qemu Qemu=1.5.2
Qemu Qemu=1.5.3
Qemu Qemu=1.6.0
Qemu Qemu=1.6.0-rc1
Qemu Qemu=1.6.0-rc2
Qemu Qemu=1.6.0-rc3
Qemu Qemu=1.6.1
Qemu Qemu=1.6.2
Qemu Qemu=1.7.1
Remediation
Patch Available
Event History
Nov 4, 2014
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-4151?
CVE-2013-4151 has a high severity rating due to the potential for remote code execution.
2
How do I fix CVE-2013-4151?
To fix CVE-2013-4151, update QEMU to version 1.7.2 or later.
3
What versions of QEMU are affected by CVE-2013-4151?
CVE-2013-4151 affects QEMU versions 1.0 through 1.7.1.
4
What are the risks associated with CVE-2013-4151?
The risks include potential remote code execution that can lead to system compromise.
5
Is there a workaround for CVE-2013-4151?
There are no official workarounds for CVE-2013-4151; the best course of action is to apply the necessary updates.