CVE-2008-4837 in the critical feed json
Stack-based buffer overflow in Microsoft Office Word 2000 SP3, 2002 SP3, 2003 SP3, and 2007 Gold and SP1; Word Viewer 2003 Gold and SP3; Of…
published 2008-12-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4816
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 37.4%
- EPSS 37.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in Microsoft Office Word 2000 SP3, 2002 SP3, 2003 SP3, and 2007 Gold and SP1; Word Viewer 2003 Gold and SP3; Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Gold and SP1; and Microsoft Works 8 allow remote attackers to execute arbitrary code via a crafted Word document that contains a malformed table property, which triggers memory corruption, aka "Word Memory Corruption Vulnerability."
Exploit prediction
37.42% 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/2008/ms08-072
vendor-advisory
-
vupen.com
/english/advisories/2008/3384
vdb-entry, vendor-advisory
- zerodayinitiative.com /advisories/ZDI-08-086/
- zerodayinitiative.com /advisories/ZDI-08-086
-
securityfocus.com
/archive/1/499064/100/0/threaded
mailing-list
-
securitytracker.com
/id?1021370
vdb-entry
-
us-cert.gov
/cas/techalerts/TA08-344A.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5982
vdb-entry, signature
Sources
- CVE List CVE-2008-4837
- NVD CVE-2008-4837
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.