CVE-2006-0007
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 · uneditedBuffer overflow in GIFIMP32.FLT, as used in Microsoft Office 2003 SP1 and SP2, Office XP SP3, Office 2000 SP3, and other products, allows user-assisted attackers to execute arbitrary code via a crafted GIF image that triggers memory corruption when it is parsed.
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 confidenceBuffer overflow in the GIFIMP32.FLT graphics filter used by Microsoft Office allows arbitrary code execution via specially crafted GIF images. The vulnerability triggers memory corruption during image parsing and requires user assistance (opening a malicious file). Affected versions include Office 2000 SP3, Office XP SP3, and Office 2003 SP1/SP2.
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= 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 Control Panel > Programs and Features, or run 'winword /?' from command line, or check registry key HKLM\Software\Microsoft\Office\Version\InstallRootAffected if Version is not 2000, 2003, or XP (or if it is one of these but not the specific SP levels)
-
Check Office service pack levelIn Office, go to Help > About Microsoft Office, or check registry under HKLM\Software\Microsoft\Office\version\SPLevel. For Office 2000/XP/2003, verify which Service Pack is installedAffected if Service Pack level is NOT 3 for Office 2000, NOT 3 for Office XP, or NOT 1/2 for Office 2003 (newer SPs are not affected)
-
Locate the GIFIMP32.FLT filter fileSearch for GIFIMP32.FLT in the Office graphics filters directory, typically found at C:\Program Files\Common Files\Microsoft Shared\GRPHFLT\ or check the equivalent path under Office installation directoryAffected if The GIFIMP32.FLT file exists on the system (vulnerability requires this filter to be present)
User is affected if running Office 2000 SP3, Office XP SP3, or Office 2003 SP1/SP2 AND the GIFIMP32.FLT graphics filter file is present on the system and gets invoked when opening GIF files.
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 dataDeploy the applicable Microsoft security update to all systems running affected Office versions; users should avoid opening untrusted GIF files from unknown sources until patches are applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0007 — 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-0007 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