dbcve.org
OfficeApplication · Microsoft

CVE-2006-0004

MEDIUM · 5.0 CVSS v2.0 Published 2006-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Microsoft PowerPoint 2000 in Office 2000 SP3 has an interaction with Internet Explorer that allows remote attackers to obtain sensitive information via a PowerPoint presentation that attempts to access objects in the Temporary Internet Files Folder (TIFF).

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 · moderate confidence

This is an information disclosure vulnerability in Microsoft PowerPoint 2000 (Office 2000 SP3) where the application, through its interaction with Internet Explorer, can be tricked into accessing and exposing files stored in the user's Temporary Internet Files folder. An attacker could embed content in a PowerPoint presentation that attempts to read cached objects (potentially including sensitive data like session tokens or cached credentials) from this folder.

MitigationApply Microsoft security update MS06-012 (or subsequent relevant patches) for Office 2000, or migrate to a supported version of Microsoft Office as Office 2000 has been end-of-life for many years. Consider restricting PowerPoint's ability to access browser cache locations via application lockdown policies.

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
OfficeApplication
Affected:= 2000

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
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify PowerPoint 2000 is installed
    Open PowerPoint, click Help menu, select About Microsoft PowerPoint. Alternatively, check Add/Remove Programs for Microsoft Office 2000 entry, or inspect the PowerPoint executable (PPT.EXE) file properties in the Office installation folder (typically C:\Program Files\Microsoft Office\Office or C:\Program Files (x86)\Microsoft Office\Office).
    Affected if The installed application is Microsoft PowerPoint 2000 (version 9.0.x) from Office 2000.
  2. Confirm Office 2000 Service Pack level
    Check the installed updates via Add/Remove Programs for 'Microsoft Office 2000 Service Pack 3' or 'Office 2000 SP3'. The vulnerability description references Office 2000 SP3 specifically.
    Affected if The system is running Office 2000 without Service Pack 3 applied, or the exact SP level cannot be verified through installed updates.
  3. Identify PowerPoint executable version
    Right-click PPT.EXE in the Office installation directory, select Properties, then check the Details tab for file version information. Expected version for PowerPoint 2000 is typically 9.0.xxxx.
    Affected if The PPT.EXE version corresponds to PowerPoint 2000 (9.0 series) and is not a later version like PowerPoint 2002, 2003, or newer.
  4. Check for MS06-012 security update
    Open Control Panel, navigate to Add/Remove Programs, enable 'Show updates', and look for 'Microsoft Office 2000 Security Update (KB912442)' or subsequent Office 2000 patches.
    Affected if The MS06-012 security update (KB912442) or a later Office 2000 security patch is NOT installed.

You are affected if PowerPoint 2000 (Office 2000, version 9.0) is installed and the MS06-012 security update has not been applied, as the vulnerability requires the unpatched Office 2000 application to be present and accessible to potential attacker-controlled presentations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security update MS06-012 (or subsequent relevant patches) for Office 2000, or migrate to a supported version of Microsoft Office as Office 2000 has been end-of-life for many years. Consider restricting PowerPoint's ability to access browser cache locations via application lockdown policies.

Fix this in Office Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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