CVE-2009-3135 in the critical feed json
Stack-based buffer overflow in Microsoft Office Word 2002 SP3 and 2003 SP3, Office 2004 and 2008 for Mac, Open XML File Format Converter fo…
published 2009-11-11 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-3118
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 35.8%
- EPSS 35.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in Microsoft Office Word 2002 SP3 and 2003 SP3, Office 2004 and 2008 for Mac, Open XML File Format Converter for Mac, Office Word Viewer 2003 SP3, and Office Word Viewer allow remote attackers to execute arbitrary code via a Word document with a malformed File Information Block (FIB) structure, aka "Microsoft Office Word File Information Memory Corruption Vulnerability."
Exploit prediction
35.79% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-068
vendor-advisory
-
vupen.com
/english/advisories/2009/3194
vdb-entry, vendor-advisory
-
secunia.com
/advisories/37277
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/36950
vdb-entry
-
osvdb.org
/59857
vdb-entry
-
us-cert.gov
/cas/techalerts/TA09-314A.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6555
vdb-entry, signature
-
securitytracker.com
/id?1023158
vdb-entry
-
labs.idefense.com
/intelligence/vulnerabilities/display.php?id=831
third-party-advisory
Sources
- CVE List CVE-2009-3135
- NVD CVE-2009-3135
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.