CVE-2009-1244 json
Unspecified vulnerability in the virtual machine display function in VMware Workstation 6.5.1 and earlier; VMware Player 2.5.1 and earlier;…
published 2009-04-13 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1243
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the virtual machine display function in VMware Workstation 6.5.1 and earlier; VMware Player 2.5.1 and earlier; VMware ACE 2.5.1 and earlier; VMware Server 1.x before 1.0.9 build 156507 and 2.x before 2.0.1 build 156745; VMware Fusion before 2.0.4 build 159196; VMware ESXi 3.5; and VMware ESX 3.0.2, 3.0.3, and 3.5 allows guest OS users to execute arbitrary code on the host OS via unknown vectors, a different vulnerability than CVE-2008-4916.
Patch / fix
Exploit prediction
2.27% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:L/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Technology feeds
References
-
securityfocus.com
/bid/34471
vdb-entry, patch
-
lists.vmware.com
/pipermail/security-announce/2009/000055.html
mailing-list, patch, vendor-advisory
-
security.gentoo.org
/glsa/glsa-201209-25.xml
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49834
vdb-entry
-
securitytracker.com
/id?1022031
vdb-entry
-
osvdb.org
/53634
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6065
vdb-entry, signature
- vmware.com /security/advisories/VMSA-2009-0006.html
-
vupen.com
/english/advisories/2009/0944
vdb-entry
-
securityfocus.com
/archive/1/502615/100/0/threaded
mailing-list
Sources
- CVE List CVE-2009-1244
- NVD CVE-2009-1244
Fencer Vulns 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.