First published: Fri May 04 2012(Updated: )
VMware Workstation 8.x before 8.0.3, VMware Player 4.x before 4.0.3, VMware Fusion 4.x through 4.1.2, VMware ESXi 3.5 through 5.0, and VMware ESX 3.5 through 4.1 do not properly configure the virtual floppy device, which allows guest OS users to cause a denial of service (out-of-bounds write operation and VMX process crash) or possibly execute arbitrary code on the host OS by leveraging administrative privileges on the guest OS.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
VMware Workstation | =8.0 | |
VMware Workstation | =8.0.1 | |
VMware Workstation | =8.0.2 | |
VMware Player | =4.0 | |
VMware Player | =4.0.1 | |
VMware Player | =4.0.2 | |
VMware Fusion Pro | =4.0 | |
VMware Fusion Pro | =4.0.1 | |
VMware Fusion Pro | =4.0.2 | |
VMware Fusion Pro | =4.1 | |
VMware Fusion Pro | =4.1.1 | |
VMware Fusion Pro | =4.1.2 | |
VMware ESXi | =3.5 | |
VMware ESXi | =3.5-1 | |
VMware ESXi | =4.0 | |
VMware ESXi | =4.0-1 | |
VMware ESXi | =4.0-2 | |
VMware ESXi | =4.0-3 | |
VMware ESXi | =4.0-4 | |
VMware ESXi | =4.1 | |
VMware ESXi | =4.1-1 | |
VMware ESXi | =4.1-2 | |
VMware ESXi | =5.0 | |
VMware ESX | =3.5 | |
VMware ESX | =3.5-update1 | |
VMware ESX | =3.5-update2 | |
VMware ESX | =3.5-update3 | |
VMware ESX | =4.0 | |
VMware ESX | =4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-2449 is considered a low severity vulnerability that can lead to a denial of service due to improper configuration of the virtual floppy device.
To fix CVE-2012-2449, upgrade VMware Workstation to version 8.0.3, VMware Player to version 4.0.3, or VMware Fusion to version 4.1.3 or later.
CVE-2012-2449 affects VMware Workstation versions 8.x before 8.0.3, VMware Player versions 4.x before 4.0.3, and multiple versions of VMware Fusion, ESXi, and ESX.
The consequences of CVE-2012-2449 include potential denial of service attacks that can disrupt guest operating system functionality.
There are no officially recommended workarounds for CVE-2012-2449 other than upgrading the affected VMware products to the latest versions.