CVE-2009-3732 in the critical feed json
Format string vulnerability in vmware-vmrc.exe build 158248 in VMware Remote Console (aka VMrc) allows remote attackers to execute arbitrar…
published 16y ago modified 4mo ago also EUVD-2009-3704
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.2%
- EPSS 16.2% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Format string vulnerability in vmware-vmrc.exe build 158248 in VMware Remote Console (aka VMrc) allows remote attackers to execute arbitrary code via unspecified vectors.
Patch / fix
- vmware ace 2.5.4
- vmware player 2.5.4
- vmware workstation 6.5.4
Is CVE-2009-3732 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-12188)
- Published
Exploit prediction
16.20% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- EDB-12188 VMware Remote Console e.x.p build-158248 - Format String dos, 2010-04-12
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-134 Use of Externally-Controlled Format String
- Technology feeds
References
-
lists.vmware.com
/pipermail/security-announce/2010/000090.html
mailing-list, patch, vendor-advisory
-
vmware.com
/security/advisories/VMSA-2010-0007.html
patch, vendor-advisory
-
security.gentoo.org
/glsa/glsa-201209-25.xml
vendor-advisory, third-party-advisory
-
archives.neohapsis.com
/archives/bugtraq/2010-04/0077.html
mailing-list, broken-link
-
secunia.com
/advisories/39110
third-party-advisory, not-applicable
-
archives.neohapsis.com
/archives/fulldisclosure/2010-04/0121.html
mailing-list, broken-link
Sources
- CVE List CVE-2009-3732
- NVD CVE-2009-3732
Fencer Intel 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.