CVE-2013-1335
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 Word 2003 SP3 and Word Viewer allow remote attackers to execute arbitrary code via crafted shape data in a Word document, aka "Word Shape 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 Word 2003 SP3 and Word Viewer where specially crafted shape data embedded in a malicious Word document can trigger arbitrary code execution. The attacker exploits the flaw by tricking a user into opening a specially crafted .doc 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= 2003all 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 if Microsoft Word 2003 is installedOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Common\InstallRoot, or use 'wmic product get name,version' to list installed Microsoft Office productsAffected if The product Microsoft Office Professional Edition 2003 or any Office 2003 edition appears in the list, or the registry key exists indicating Office 2003 is installed
-
Determine the exact Word 2003 versionLocate WINWORD.EXE in the Office11 folder (typically C:\Program Files\Microsoft Office\Office11\ or C:\Program Files (x86)\Microsoft Office\Office11\) and right-click to view Properties, or run 'wmic product where "name like 'Microsoft Office%2003%'" get version'Affected if The version shown is any release of Word 2003 (version 11.x), as all versions of Word 2003 are affected
-
Check if Word Viewer is installedLook for Microsoft Office Word Viewer in Add/Remove Programs (appwiz.cpl), or check for the installation folder typically at C:\Program Files\Microsoft Office\WordViewer\Affected if Microsoft Office Word Viewer appears in installed programs, as all versions are affected regardless of version number
-
Verify the product edition is specifically Word 2003In Registry Editor, check HKEY_CLASSES_ROOT\Word.Application\CurVer to confirm the default value is Word.Application.11, or open Word and go to Help > About Microsoft Office Word to see the version number 11.xAffected if The version displays as 11.x (Office 2003/Word 2003), indicating a vulnerable version
You are affected if Microsoft Word 2003 (any SP level) or any version of Microsoft Office Word Viewer is installed on your system.
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 update MS13-063 or upgrade to a supported version of Microsoft Office, as Word 2003 is end-of-life. Avoid opening untrusted Word documents from unknown sources.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1335 — 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-2013-1335 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