CVE-2009-0224 in the critical feed json
Microsoft Office PowerPoint 2000 SP3, 2002 SP3, 2003 SP3, and 2007 SP1 and SP2; PowerPoint Viewer 2003 and 2007 SP1 and SP2; PowerPoint in…
published 2009-05-12 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0232
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 30.1%
- EPSS 30.1% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Microsoft Office PowerPoint 2000 SP3, 2002 SP3, 2003 SP3, and 2007 SP1 and SP2; PowerPoint Viewer 2003 and 2007 SP1 and SP2; PowerPoint in Microsoft Office 2004 for Mac and 2008 for Mac; Open XML File Format Converter for Mac; Microsoft Works 8.5 and 9.0; and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP1 and SP2 do not properly validate PowerPoint files, which allows remote attackers to execute arbitrary code via multiple crafted BuildList records that include ChartBuild containers, which triggers memory corruption, aka "Memory Corruption Vulnerability."
Exploit prediction
30.08% 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-94 Improper Control of Generation of Code
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-017
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6023
vdb-entry, signature
-
secunia.com
/advisories/32428
third-party-advisory
-
vupen.com
/english/advisories/2009/1290
vdb-entry
-
securityfocus.com
/bid/34879
vdb-entry
-
labs.idefense.com
/intelligence/vulnerabilities/display.php?id=793
third-party-advisory
-
securitytracker.com
/id?1022205
vdb-entry
-
us-cert.gov
/cas/techalerts/TA09-132A.html
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2009-0224
- NVD CVE-2009-0224
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.