Skip to content
Fencer Vulns
critical 10.0

CVE-2008-3892 in the critical feed json

Buffer overflow in a certain ActiveX control in the COM API in VMware Workstation 5.5.x before 5.5.8 build 108000, VMware Workstation 6.0.x…

published 2008-09-03 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3878

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
24.4%
EPSS 24.4% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

Buffer overflow in a certain ActiveX control in the COM API in VMware Workstation 5.5.x before 5.5.8 build 108000, VMware Workstation 6.0.x before 6.0.5 build 109488, VMware Player 1.x before 1.0.8 build 108000, VMware Player 2.x before 2.0.5 build 109488, VMware ACE 1.x before 1.0.7 build 108880, VMware ACE 2.x before 2.0.5 build 109488, and VMware Server before 1.0.7 build 108231 allows remote attackers to cause a denial of service (browser crash) or possibly execute arbitrary code via a call to the GuestInfo method in which there is a long string argument, and an assignment of a long string value to the result of this call. NOTE: this may overlap CVE-2008-3691, CVE-2008-3692, CVE-2008-3693, CVE-2008-3694, CVE-2008-3695, or CVE-2008-3696.

Patch / fix

  • vmware ace 1.0.7, 2.0.5
  • vmware player 1.0.8, 2.0.5
  • vmware server 1.0.7
  • vmware workstation 5.5.8, 6.0.5

Timeline

  1. First public exploit (EDB-6345)
  2. Published

Exploit prediction

24.36% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-6345 VMware - COM API ActiveX Remote Buffer Overflow (PoC) dos, 2008-09-01

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Technology feeds

References

Sources

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.