CVE-2010-3336
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 Office XP SP3, Office 2004 and 2008 for Mac, Office for Mac 2011, and Open XML File Format Converter for Mac allow remote attackers to execute arbitrary code via a crafted Office document that triggers memory corruption, aka "MSO Large SPID Read AV 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 confidenceMemory corruption vulnerability in Microsoft Office's handling of specially crafted Office documents (Open XML format), allowing remote attackers to execute arbitrary code via a Large SPID (Service Pack ID) Read Access Violation when the application processes malformed document content.
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= 2004= 2008= 2011= xpall 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.
-
Identify installed Microsoft Office versionOpen Control Panel > Programs and Features, or run 'winver' command, or check the executable properties of WINWORD.EXE (typically in C:\Program Files\Microsoft Office\OfficeXX\ or C:\Program Files (x86)\Microsoft Office\OfficeXX\)Affected if The installed version is Microsoft Office 2004, 2008, 2011, or XP (any edition)
-
Check for Open XML File Format Converter installationLook in Control Panel > Programs and Features for 'Microsoft Open XML File Format Converter', or check Program Files folders for 'Open XML Converter' executableAffected if Microsoft Open XML File Format Converter is installed (any version)
-
Verify Office Open XML file handling componentExamine the file version of the Office Open XML parsing component (msoshext.dll or similar Office DLLs in the Office installation directory) for the specific version numbersAffected if The Office DLLs match versions from 2004, 2008, 2011, or XP without security updates applied
-
Check for applied security updatesView installed updates in Control Panel > Programs > Programs and Features > View installed updates, or run 'wmic qfe list' command to list installed hotfixesAffected if No security updates from MS10-087 or related Office security bulletins are installed
-
Confirm Open XML document processing capabilityVerify that the Office installation includes Open XML format support (default in Office 2007 and later, or via Open XML Converter for Office 2004/2008/XP)Affected if Open XML document handling is enabled or the Open XML Converter is present
A system is affected if it runs Microsoft Office 2004, 2008, 2011, or XP (or has the Open XML File Format Converter installed) without the MS10-087 or subsequent security updates applied.
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 (MS10-087 and related patches) to all affected Office installations; avoid opening untrusted Office documents from untrusted sources as a defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3336 — 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-3336 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