CVE-2010-3335
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 2003 SP3, Office 2007 SP2, Office 2010, 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 "Drawing Exception Handling 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 drawing exception handling component allows remote code execution when users open specially crafted Office documents containing malformed drawing objects. The vulnerability affects multiple Office versions across Windows and Mac platforms.
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= 2003= 2004= 2007= 2008= 2010= 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 version on WindowsOpen Control Panel > Programs and Features, find Microsoft Office entry and note the version number, or run 'reg query "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\ProgramPaths\Office16"' or earlier version paths. Alternatively, open any Office app, go to File > Account > About [App] to see exact build number.Affected if Version matches 2003, 2007, 2010, or XP without MS10-087 installed
-
Identify installed Microsoft Office version on MacOpen any Office application on Mac, go to [App] > About [App] and note the full version number displayed.Affected if Version matches 2004, 2008, or 2011 without corresponding security update installed
-
Verify if security update MS10-087 is applied on WindowsOpen Control Panel > Programs and Features, click 'View installed updates' and search for 'MS10-087' or security update KB2293194. Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\Updates\UpdateExeVolatile"' or check Windows Update history.Affected if MS10-087 (KB2293194) or subsequent relevant update is NOT installed
-
Check for Microsoft Open XML File Format Converter installationOn Mac, check /Applications folder for 'Microsoft Open XML File Format Converter' or search using Spotlight. On Windows, check Programs and Features list.Affected if Open XML File Format Converter of any version is installed without MS10-087 applied to underlying Office installation
User is affected if running an affected Office version (2003, 2004, 2007, 2008, 2010, 2011, XP) or Open XML File Format Converter AND security update MS10-087 has not been 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.
dbcve · scopedApply Microsoft security update MS10-087 (or subsequent relevant updates) to all affected Office installations. Until patched, avoid opening untrusted Office documents from unknown sources.
Microsoft Office 2016 or later / Microsoft 365
- Upgrade to a later Microsoft Office version that receives security updates
- For legacy systems no longer supported by Microsoft, migrate to Microsoft 365 or LibreOffice
- Apply any available Microsoft Security Updates for this vulnerability if still supported by Microsoft
Generated from the published advisory — verify against the referenced sources before acting.
- 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-3335 — 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-3335 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