CVE-2010-1139 json
Format string vulnerability in vmrun in VMware VIX API 1.6.x, VMware Workstation 6.5.x before 6.5.4 build 246459, VMware Player 2.5.x befor…
published 16y ago modified 4mo ago also EUVD-2010-1170
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
Format string vulnerability in vmrun in VMware VIX API 1.6.x, VMware Workstation 6.5.x before 6.5.4 build 246459, VMware Player 2.5.x before 2.5.4 build 246459, and VMware Server 2.x on Linux, and VMware Fusion 2.x before 2.0.7 build 246742, allows local users to gain privileges via format string specifiers in process metadata.
Patch / fix
Is CVE-2010-1139 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 FencerExploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/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
-
secunia.com
/advisories/39206
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/39201
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/39215
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/39407
vdb-entry
-
archives.neohapsis.com
/archives/bugtraq/2010-04/0077.html
mailing-list
-
osvdb.org
/63606
vdb-entry
-
securitytracker.com
/id?1023835
vdb-entry
-
archives.neohapsis.com
/archives/fulldisclosure/2010-04/0121.html
mailing-list
Sources
- CVE List CVE-2010-1139
- NVD CVE-2010-1139
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.