CVE-2007-3030
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 · uneditedMicrosoft Excel 2000 SP3, 2002 SP3, 2003 SP2, and 2003 Viewer allows user-assisted remote attackers to execute arbitrary code via a malformed Excel file involving the "denoting [of] the start of a Workspace designation", which results in memory corruption, aka the "Workbook Memory Corruption Vulnerability".
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 confidenceThis is a memory corruption vulnerability in Microsoft Excel versions 2000 SP3 through 2003 SP2 and the 2003 Viewer. The flaw occurs during parsing of malformed Excel files when processing the 'start of a Workspace designation', which leads to memory corruption and allows arbitrary code execution. The attack requires user assistance, specifically that the victim open a specially crafted malicious Excel 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= 2007= 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/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 Excel versionOpen Excel, go to Help > About Microsoft Excel, or check Add/Remove Programs for the installed version. On Windows, also check the executable properties of C:\Program Files\Microsoft Office\OfficeXX\EXCEL.EXE (where XX is the office version number).Affected if The installed version is Excel 2000, 2002, 2003, 2004 for Mac, or 2007, AND the version is before any post-2003 SP2 security updates.
-
Check Excel service pack levelIn Excel, go to Help > About to view the full version string including SP level. For Excel 2000, look for 'SP3' specifically; for Excel 2002, any SP; for Excel 2003, verify if it is SP2 or lower.Affected if Excel 2000 is at SP3 or Excel 2003 is at SP2 or earlier, as these are within the vulnerable range stated in the summary.
-
Identify Microsoft Excel Viewer installationCheck for the presence of Excel Viewer (XLVIEW.EXE) in typical locations such as C:\Program Files\Microsoft Office\Office\ or check Add/Remove Programs for 'Microsoft Excel Viewer'.Affected if Microsoft Excel Viewer 2003 is installed, as this is explicitly listed as affected.
-
Determine if file parsing features are accessibleThe vulnerability triggers when parsing the 'start of a Workspace designation' in malformed Excel files. Verify whether Excel can open files from external or untrusted sources by default - this is the attack vector.Affected if Users can open Excel files from any source, as the vulnerability requires a specially crafted malicious file to be opened.
You are affected if you have Excel 2000 SP3 through Excel 2003 SP2 or Excel Viewer 2003 installed and users open Excel files, since the memory corruption occurs during Workspace designation parsing of malformed 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 dataApply Microsoft security updates for this vulnerability. Users should not open Excel files from untrusted sources, and organizations should implement email gateway filtering for suspicious attachments.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3030 — 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-3030 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