CVE-2008-0113 in the critical feed json
Unspecified vulnerability in Microsoft Office Excel Viewer 2003 up to SP3 allows user-assisted remote attackers to execute arbitrary code v…
published 2008-03-11 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-0126
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 42.2%
- EPSS 42.2% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
Unspecified vulnerability in Microsoft Office Excel Viewer 2003 up to SP3 allows user-assisted remote attackers to execute arbitrary code via an Excel document with malformed cell comments that trigger memory corruption from an "allocation error," aka "Microsoft Office Cell Parsing Memory Corruption Vulnerability."
Timeline
- Published
- First public exploit (EDB-5320)
Exploit prediction
42.23% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-5320 Microsoft Office XP SP3 - '.PPT' File Buffer Overflow (MS08-016) local, 2008-03-30
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-94 Improper Control of Generation of Code
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2008/ms08-016
vendor-advisory
-
marc.info
/?l=bugtraq&m=120585858807305&w=2
vendor-advisory
-
secunia.com
/advisories/29321
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2008/0848/references
vdb-entry, vendor-advisory
- zerodayinitiative.com /advisories/ZDI-08-008
-
us-cert.gov
/cas/techalerts/TA08-071A.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A5421
vdb-entry, signature
-
securityfocus.com
/archive/1/489415/100/0/threaded
mailing-list
-
securitytracker.com
/id?1019578
vdb-entry
Sources
- CVE List CVE-2008-0113
- NVD CVE-2008-0113
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.