dbcve.org
Ovf ToolApplication · VMware

CVE-2012-3569

HIGH · 9.3 CVSS v2.0 Published 2012-11-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
Format string vulnerability in VMware OVF Tool 2.1 on Windows, as used in VMware Workstation 8.x before 8.0.5, VMware Player 4.x before 4.0.5, and other products, allows user-assisted remote attackers to execute arbitrary code via a crafted OVF file.

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

A detailed technical summary for this CVE is being prepared.

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
Ovf ToolApplication
Affected:= 2.1
WorkstationApplication
Affected:= 8.0= 8.0.0.18997= 8.0.1= 8.0.1.27038= 8.0.2= 8.0.3= 8.0.4
PlayerApplication
Affected:= 4.0= 4.0.0.18997= 4.0.1= 4.0.2= 4.0.3= 4.0.4

CVSS 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
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.vmware.com →
Recommended fix High confidence

VMware Workstation 8.0.5+, VMware Player 4.0.5+, VMware OVF Tool 2.1.1+

  1. 1. Obtain the fixed versions from the VMware security advisory at http://www.vmware.com/security/advisories/VMSA-2012-0015.html
  2. 2. For VMware Workstation: upgrade to version 8.0.5 or later
  3. 3. For VMware Player: upgrade to version 4.0.5 or later
  4. 4. For VMware OVF Tool: upgrade to the corresponding patched version (2.1.1 or later as indicated in VMSA-2012-0015)
  5. 5. Download the appropriate installer for your platform from the VMware website
  6. 6. Run the installer and follow the prompts to complete the upgrade
  7. 7. Restart any VMware services if prompted
  8. 8. Verify the installed version matches the fixed release
Caveat Minor version upgrades within the same major release typically maintain compatibility; however, test OVF file parsing in your environment after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-3569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-3569 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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