dbcve.org
AceApplication · VMware

CVE-2007-0061

HIGH · 10.0 CVSS v2.0 Published 2007-09-21
Fix available
A fix is available. Upgrade to 1.0.3 / 1.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The DHCP server in EMC VMware Workstation before 5.5.5 Build 56455 and 6.x before 6.0.1 Build 55017, Player before 1.0.5 Build 56455 and Player 2 before 2.0.1 Build 55017, ACE before 1.0.3 Build 54075 and ACE 2 before 2.0.1 Build 55017, and Server before 1.0.4 Build 56528 allows remote attackers to execute arbitrary code via a malformed packet that triggers "corrupt stack memory."

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
How this class of weakness works · CWE-119

The program reads or writes outside the bounds of an allocated buffer, corrupting adjacent memory. With crafted input an attacker can overwrite control data and, with effort, redirect execution to their own code. Remediation ranges from bounds checking and safe library functions to compiler mitigations, usually alongside a careful audit of the surrounding code.

General guidance for the memory buffer bounds error class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
AceApplication
Affected:>= 1.0, < 1.0.3>= 2.0, < 2.0.1
PlayerApplication
Affected:>= 1.0, < 1.0.5>= 2.0, < 2.0.1
ServerApplication
Affected:>= 1.0, < 1.0.4
WorkstationApplication
Affected:>= 5.5, < 5.5.5>= 6.0, < 6.0.1
EsxOperating system
Affected:= 2.0.2= 2.1.3= 2.5.3= 2.5.4= 3.0.0= 3.0.1
Ubuntu LinuxOperating system
Affected:= 6.06= 6.10= 7.04

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
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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
Upgrade available Upgrade to 1.0.3 / 1.0.4 / 1.0.5 or later
Fixed in 1.0.31.0.41.0.5
Vendor patch www.iss.net →
Recommended fix High confidence

VMware Workstation 5.5.5/6.0.1, Player 1.0.5/2.0.1, ACE 1.0.3/2.0.1, or Server 1.0.4 (with matching Build numbers)

  1. Identify the exact VMware product (Workstation, Player, ACE, or Server) and current version in use
  2. For VMware Workstation: upgrade to version 5.5.5 (Build 56455) or 6.0.1 (Build 55017) depending on your major version branch
  3. For VMware Player: upgrade to version 1.0.5 (Build 56455) or 2.0.1 (Build 55017) depending on your major version branch
  4. For VMware ACE: upgrade to version 1.0.3 (Build 54075) or 2.0.1 (Build 55017) depending on your major version branch
  5. For VMware Server: upgrade to version 1.0.4 (Build 56528)
  6. Obtain the upgrade from official VMware download channels and verify the build number matches the fixed release
  7. Apply the upgrade following standard VMware installation procedures
  8. Restart the VMware services to ensure the patched DHCP server component is loaded
Caveat Upgrades between major VMware versions may require virtual machine migration considerations; test in non-production environment first

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0061 — 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-2007-0061 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