FusionApplication · VMware
CVE-2015-2337
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTPInt.dll in VMware Workstation 10.x before 10.0.6 and 11.x before 11.1.1, VMware Player 6.x before 6.0.6 and 7.x before 7.1.1, and VMware Horizon Client 3.2.x before 3.2.1, 3.3.x, and 5.x local-mode before 5.4.2 on Windows does not properly allocate memory, which allows guest OS users to execute arbitrary code on the host OS via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA memory allocation vulnerability in TPInt.dll in VMware Workstation, Player, and Horizon Client on Windows allows a guest OS user to execute arbitrary code on the host OS, enabling a virtualization escape. The vulnerability stems from improper memory handling in the TPInt component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FusionApplication
= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 7.0= 7.0.1
PlayerApplication
= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 7.0= 7.1
WorkstationApplication
= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.0.5= 11.0= 11.1
Horizon ClientApplication
= 3.2.0= 3.3
Horizon View ClientApplication
= 5.4= 5.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed VMware productOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, to list installed VMware products such as VMware Workstation, Player, Fusion, or Horizon ClientAffected if Any VMware product from the affected list is installed on Windows
-
Check VMware versionRun 'vmware -v' from command line, or open the VMware application and go to Help > About, or check the Windows Registry key HKLM\SOFTWARE\VMware, Inc.\VMware desktop\InstallPathAffected if Version matches: Workstation 10.0.x or 11.0-11.1, Player 6.0.x or 7.0-7.1, Fusion 6.0.x or 7.0-7.0.1, Horizon Client 3.2.0 or 3.3, Horizon View Client 5.4 or 5.4.1
-
Verify TPInt.dll is presentLocate the VMware installation directory (typically C:\Program Files\VMware\VMware Workstation\ or similar for other products), then search for TPInt.dll file in that folderAffected if TPInt.dll exists in the VMware installation directory, confirming the vulnerable component is present
-
Confirm host OS is WindowsRun 'systeminfo | findstr /B /C:OS Name' or check System Properties, as this vulnerability only affects Windows hostsAffected if The host operating system is Windows
If a vulnerable VMware product version is installed on Windows with TPInt.dll present, the environment is affected by CVE-2015-2337.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate affected VMware products to the following versions: Workstation to 10.0.6 or 11.1.1+, Player to 6.0.6 or 7.1.1+, and Horizon Client to 3.2.1+, 5.4.2+ respectively.
Fix this in Fusion
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-2337 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data