QEMU 'virtio_load()' Function Memory Corruption Vulnerability
BID:66976
Info
QEMU 'virtio_load()' Function Memory Corruption Vulnerability
| Bugtraq ID: | 66976 |
| Class: | Design Error |
| CVE: |
CVE-2014-0182 |
| Remote: | No |
| Local: | Yes |
| Published: | Apr 17 2014 12:00AM |
| Updated: | Mar 19 2015 08:07AM |
| Credit: | Petr Matousek |
| Vulnerable: |
Ubuntu Ubuntu Linux 12.04 LTS i386 Ubuntu Ubuntu Linux 12.04 LTS amd64 Ubuntu Ubuntu Linux 10.04 sparc Ubuntu Ubuntu Linux 10.04 powerpc Ubuntu Ubuntu Linux 10.04 i386 Ubuntu Ubuntu Linux 10.04 ARM Ubuntu Ubuntu Linux 10.04 amd64 Red Hat Enterprise Linux Workstation 6 Red Hat Enterprise Linux Server 6 Red Hat Enterprise Linux HPC Node 6 Red Hat Enterprise Linux Desktop 6 QEMU QEMU 0 CentOS CentOS 6 |
| Not Vulnerable: | |
Discussion
QEMU 'virtio_load()' Function Memory Corruption Vulnerability
QEMU is prone to a local memory-corruption vulnerability.
An attacker on the guest operating system can exploit this issue to execute arbitrary code in the host operating system in the context of affected application.
QEMU is prone to a local memory-corruption vulnerability.
An attacker on the guest operating system can exploit this issue to execute arbitrary code in the host operating system in the context of affected application.
Exploit / POC
QEMU 'virtio_load()' Function Memory Corruption Vulnerability
Currently we are not aware of any working exploits. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Currently we are not aware of any working exploits. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Solution / Fix
QEMU 'virtio_load()' Function Memory Corruption Vulnerability
Solution:
Currently, we are not aware of any vendor-supplied patches. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].
Solution:
Currently, we are not aware of any vendor-supplied patches. If you feel we are in error or are aware of more recent information, please mail us at: [email protected].