CVE-2006-4694
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 · uneditedUnspecified vulnerability in PowerPoint in Microsoft Office 2000, Office XP and Office 2003 allows user-assisted attackers to execute arbitrary code via a crafted record in a PPT file, as exploited by malware such as Exploit:Win32/Controlppt.W, Exploit:Win32/Controlppt.X, and Exploit-PPT.d/Trojan.PPDropper.F. NOTE: it has been reported that the attack vector involves SlideShowWindows.View.GotoNamedShow.
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 confidenceMemory corruption vulnerability in PowerPoint allows arbitrary code execution via specially crafted PPT files containing malformed records. The attack vector specifically involves the SlideShowWindows.View.GotoNamedShow method and requires user-assisted interaction (opening a malicious file). Known exploited by multiple malware families including Controlppt and Trojan.PPDropper.
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= 2000= 2003= xpCVSS 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
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 Microsoft Office versionOpen PowerPoint, click Help menu, select About Microsoft Office PowerPoint. Note the exact version number (e.g., 10.0 for XP, 11.0 for 2003, 9.0 for 2000). Alternatively, check Add/Remove Programs for Microsoft Office installation.Affected if Version is 9.0 (Office 2000), 10.0 (Office XP), or 11.0 (Office 2003)
-
Confirm PowerPoint component is presentVerify PowerPoint executable exists at typical installation path: C:\Program Files\Microsoft Office\Office10\POWERPNT.exe (path varies by version - Office10 for XP, Office11 for 2003, Office9 for 2000).Affected if PowerPoint executable is found without corresponding security updates installed
-
Check for CVE-2006-4694 specific security updateOpen PowerPoint, go to Help > Check for Updates, or manually verify if security update KB925528 (or subsequent Office security rollups) has been installed via Control Panel > Add or Remove Programs > Show Updates.Affected if The specific security update for this CVE is NOT installed and Office version matches affected versions (2000, XP, 2003)
-
Verify vulnerability trigger condition existsThis CVE exploits the SlideShowWindows.View.GotoNamedShow method through malformed PPT records. Check if PowerPoint can open files from untrusted sources - inspect file association settings for .ppt files and macro security settings (Tools > Macro > Security).Affected if User can open PowerPoint files from any source and the vulnerable method is accessible without additional security constraints
A user is affected if they have Microsoft Office PowerPoint versions 2000, XP, or 2003 installed without the CVE-2006-4694 security update applied.
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 updates for affected Office versions (2000, XP, 2003); block or exercise extreme caution with untrusted PPT attachments; disable macro/autoplay features in Office.
- 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-2006-4694 — 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-2006-4694 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