CVE-2007-0065
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 · uneditedHeap-based buffer overflow in Object Linking and Embedding (OLE) Automation in Microsoft Windows 2000 SP4, XP SP2, Server 2003 SP1 and SP2, Vista, Office 2004 for Mac, and Visual basic 6.0 SP6 allows remote attackers to execute arbitrary code via a crafted script request.
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 confidenceHeap-based buffer overflow vulnerability in Windows OLE Automation allows remote code execution via crafted script requests. The flaw occurs when OLE Automation processes malformed script requests, enabling attackers to overflow heap memory and execute arbitrary code. Affected components span multiple Windows versions (2000 SP4 through Vista) and Visual Basic 6.0 SP6.
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 dataall versions= 6.0CVSS 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
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.
-
Check for Visual Basic 6.0 installationVerify if Microsoft Visual Basic 6.0 is installed on the system. Check program files or use registry query for VB6 installation key.Affected if Visual Basic 6.0 is installed (version 6.0 specifically)
-
Confirm OLE Automation component is presentVerify the OLE Automation system component is available on the Windows system. This is typically a core Windows component present by default.Affected if OLE Automation is present and accessible to script processing engines
-
Identify script execution pointsInventory applications or services that utilize OLE Automation to process script requests, such as VBScript, JScript, or third-party script engines.Affected if Any application uses OLE Automation to handle script requests from external or untrusted sources
-
Check for Microsoft Office installationDetermine if Microsoft Office is installed, as all versions are affected according to the CVE scope.Affected if Microsoft Office of any version is installed and OLE Automation is used by Office applications
-
Review script request handlingExamine configuration and permissions around script execution - check if script requests can reach OLE Automation from network or untrusted sources.Affected if OLE Automation can process script requests from remote or untrusted sources
The environment is affected if Visual Basic 6.0 is installed, or if Microsoft Office is present, and OLE Automation is enabled to process script requests (particularly from remote or untrusted sources).
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 dataApply Microsoft security patches for CVE-2007-0065 to all affected systems. For legacy systems no longer supported by Microsoft, consider removing Visual Basic 6.0 SP6 or implementing network-level filtering to block untrusted script execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0065 — 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-2007-0065 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