CVE-2010-1245
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 Office Excel 2002 SP3, Office 2004 for Mac, Office 2008 for Mac, and Open XML File Format Converter for Mac allows remote attackers to execute arbitrary code via an Excel file with a malformed SxView (0xB0) record, aka "Excel Record Memory Corruption Vulnerability," a different vulnerability than CVE-2010-0824 and CVE-2010-0821.
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 Microsoft Excel allows remote code execution via specially crafted Excel files containing malformed SxView (0xB0) records. The vulnerability affects Excel 2002 SP3 and multiple Mac Office versions. Successful exploitation gives attackers arbitrary code execution capabilities.
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= 2002= 2004= 2008all versionsCVSS 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.
-
Check installed Microsoft Excel versionOpen Excel, go to Help > About Microsoft Excel, or run: winword.exe /? (for Office) or check Add/Remove Programs for Excel versionAffected if Version is Excel 2002 (any service pack)
-
Check installed Microsoft Office versionOpen any Office app, go to Help > About, or check Add/Remove Programs for Office versionAffected if Version is Office 2004 (Mac) or Office 2008 (Mac)
-
Check if Microsoft Open Xml File Format Converter is installedCheck Add/Remove Programs (Windows) or Applications folder (Mac) for 'Microsoft Open XML File Format Converter' entryAffected if Converter is installed (all versions are affected)
-
Verify Excel file handling is enabledConfirm Excel is set as the default handler for .xls files, or the Open XML File Format Converter is active for file conversionsAffected if Excel or the converter processes .xls/.xlsx files
User is affected if Excel 2002, Office 2004, Office 2008, or Open XML File Format Converter is installed and the system handles Excel 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.
dbcve · scopedApply Microsoft security updates for the affected Office products and exercise caution when opening Excel files from untrusted sources.
Microsoft Office 2010 or later (including Microsoft 365) for Windows; Microsoft Office 2011 for Mac or later
- Apply Microsoft Security Bulletin MS10-038 which addresses CVE-2010-1245
- For Excel 2002 SP3: Install security update KB983316 from Microsoft Update
- For Office 2004 for Mac: Install security update from Microsoft or migrate to newer Office version
- For Office 2008 for Mac: Install security update from Microsoft or migrate to newer Office version
- For Open XML File Format Converter for Mac: Uninstall or replace with supported alternatives
- Verify no Excel files from untrusted sources are opened until patches are applied
- After patching, validate system is protected by reviewing installed updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1245 — 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-2010-1245 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