CVE-2009-0910 json
Heap-based buffer overflow in the VNnc Codec in VMware Workstation 6.5.x before 6.5.2 build 156735, VMware Player 2.5.x before 2.5.2 build…
published 2009-04-06 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0907
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Heap-based buffer overflow in the VNnc Codec in VMware Workstation 6.5.x before 6.5.2 build 156735, VMware Player 2.5.x before 2.5.2 build 156735, VMware ACE 2.5.x before 2.5.2 build 156735, and VMware Server 2.0.x before 2.0.1 build 156745 allows remote attackers to execute arbitrary code via a crafted web page or video file, aka ZDI-CAN-436.
Patch / fix
Exploit prediction
2.81% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/bid/34373 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
-
seclists.org
/fulldisclosure/2009/Apr/0036.html
mailing-list, patch
-
lists.vmware.com
/pipermail/security-announce/2009/000054.html
mailing-list, patch, vendor-advisory
-
securityfocus.com
/bid/34373
vdb-entry, exploit
-
security.gentoo.org
/glsa/glsa-201209-25.xml
vendor-advisory
-
vupen.com
/english/advisories/2009/0944
vdb-entry
- vmware.com /security/advisories/VMSA-2009-0005.html
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5786
vdb-entry, signature
-
securitytracker.com
/id?1021974
vdb-entry
Sources
- CVE List CVE-2009-0910
- NVD CVE-2009-0910
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.