CVE-2008-3761 json
hcmon.sys in VMware Workstation 6.5.1 and earlier, VMware Player 2.5.1 and earlier, VMware ACE 2.5.1 and earlier, and VMware Server 1.0.x b…
published 2008-08-21 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3747
- cvss
- 4.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 1
- Exploit-DB
Summary
hcmon.sys in VMware Workstation 6.5.1 and earlier, VMware Player 2.5.1 and earlier, VMware ACE 2.5.1 and earlier, and VMware Server 1.0.x before 1.0.9 build 156507 and 2.0.x before 2.0.1 build 156745 uses the METHOD_NEITHER communication method for IOCTLs, which allows local users to cause a denial of service via a crafted IOCTL request.
Timeline
- First public exploit (EDB-6262)
- Published
Exploit prediction
1.00% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-6262 VMware Workstation 6.5.1 - 'hcmon.sys 6.0.0.45731' Local Denial of Service dos, 2008-08-18
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.9 | AV:L/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
exploit-db.com
/exploits/6262
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44539
vdb-entry
-
securityreason.com
/securityalert/4177
third-party-advisory
-
seclists.org
/fulldisclosure/2009/Apr/0036.html
mailing-list
-
securityfocus.com
/bid/30737
vdb-entry
-
securityfocus.com
/bid/34373
vdb-entry
-
securitytracker.com
/id?1020715
vdb-entry
- orange-bat.com /adv/2008/adv.08.17.txt
-
vupen.com
/english/advisories/2009/0944
vdb-entry
-
lists.vmware.com
/pipermail/security-announce/2009/000054.html
mailing-list
- vmware.com /security/advisories/VMSA-2009-0005.html
Sources
- CVE List CVE-2008-3761
- NVD CVE-2008-3761
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.