CVE-2006-3867
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 Microsoft Excel 2000, 2002, 2003, 2004 for Mac, v.X for Mac, and Excel Viewer 2003 allows user-assisted attackers to execute arbitrary code via a crafted Lotus 1-2-3 file, a different vulnerability than CVE-2006-2387 and CVE-2006-3875.
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 confidenceMemory corruption vulnerability in Microsoft Excel when parsing specially crafted Lotus 1-2-3 spreadsheet files, allowing arbitrary code execution via user-assisted attack vector (user must open malicious file).
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= 2002= 2003= 2004= x= 2003CVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/Au:N/C:P/I:P/A:P
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 Excel versionOn Windows, open Excel, go to Help > About Microsoft Excel to see version number, or check Excel.exe properties in Program Files/Microsoft Office. On Mac, right-click Excel.app > Get Info to see version.Affected if Version displayed is 2000, 2002, 2003, 2004 (Mac), or X (Mac)
-
Check for Microsoft Excel Viewer 2003Check if Excel Viewer 2003 is installed by looking in Add/Remove Programs (Windows) or by locating the Excel Viewer application in Program Files.Affected if Microsoft Excel Viewer 2003 is installed
-
Verify Lotus 1-2-3 file import capability presentOpen Excel and attempt to open a .123 file (Lotus 1-2-3 format) via File > Open. If Excel displays import options or converts the file, the Lotus filter is present. Alternatively, check for lotus123.xls or similar filter files in the Excel installation folder.Affected if Excel can open and parse Lotus 1-2-3 (.123) files, indicating the vulnerable filter is loaded
System is affected if Microsoft Excel (2000, 2002, 2003, 2004 for Mac, or Excel X for Mac) or Excel Viewer 2003 is installed AND the Lotus 1-2-3 import filter is present and functional, allowing a user to open a malicious .123 file.
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 affected Excel versions; instruct users not to open untrusted or unexpected Lotus 1-2-3 attachments; implement email gateway filtering for .123 files from external sources.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3867 — 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-3867 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