CVE-2009-0199
What it is
Heap-based buffer overflow in the VMnc media codec in vmnc.dll in VMware Movie Decoder before 6.5.3 build 185404, VMware Workstation 6.5.x before 6.5.3 build 185404, VMware Player 2.5.x before 2.5.3 build 185404, and VMware ACE 2.5.x before 2.5.3 build 185404 on Windows might allow remote attackers to execute arbitrary code via a video file with crafted dimensions (aka framebuffer parameters).
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 5.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 5.0% in the next 30 days (EPSS).
- Severity: 9.3 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 5.0% · EPSS, next 30 days
- Weakness
- CWE-119 · Buffer errors
- Record status
- Modified
Affected
- VMware Ace 2.5.0
- VMware Ace 2.5.1
- VMware Ace 2.5.2
- VMware Movie Decoder 6.5.3
- VMware Player 2.5
- VMware Player 2.5.1
- VMware Player 2.5.2
- VMware Player 2.5.2_build_156735
Attack profile CVSS 2.0 · 9.3
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
Raw vector
AV:N/AC:M/Au:N/C:C/I:C/A:C
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2009-0199.md and follow it. Check whether this project is affected by CVE-2009-0199. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://lists.vmware.com/pipermail/security-announce/2009/000065.html
- http://secunia.com/advisories/34938
- http://secunia.com/secunia_research/2009-25/
- http://www.vmware.com/security/advisories/VMSA-2009-0012.html
- http://www.vupen.com/english/advisories/2009/2553
- http://lists.vmware.com/pipermail/security-announce/2009/000065.html
- http://secunia.com/advisories/34938
- http://secunia.com/secunia_research/2009-25/
- http://www.vmware.com/security/advisories/VMSA-2009-0012.html
- http://www.vupen.com/english/advisories/2009/2553
References
- http://lists.vmware.com/pipermail/security-announce/2009/000065.html
- http://secunia.com/advisories/34938
- http://secunia.com/secunia_research/2009-25/
- http://www.securityfocus.com/archive/1/506286/100/0/threaded
- http://www.securityfocus.com/bid/36290
- http://www.vmware.com/security/advisories/VMSA-2009-0012.html
- http://www.vupen.com/english/advisories/2009/2553
- http://lists.vmware.com/pipermail/security-announce/2009/000065.html
- http://secunia.com/advisories/34938
- http://secunia.com/secunia_research/2009-25/
- http://www.securityfocus.com/archive/1/506286/100/0/threaded
- http://www.securityfocus.com/bid/36290
- http://www.vmware.com/security/advisories/VMSA-2009-0012.html
- http://www.vupen.com/english/advisories/2009/2553