CVE-2009-0226 in the critical feed json
Stack-based buffer overflow in the PowerPoint 4.2 conversion filter in Microsoft Office PowerPoint 2000 SP3, 2002 SP3, and 2003 SP3 allows…
published 2009-05-12 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0234
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 34.8%
- EPSS 34.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in the PowerPoint 4.2 conversion filter in Microsoft Office PowerPoint 2000 SP3, 2002 SP3, and 2003 SP3 allows remote attackers to execute arbitrary code via a long string in sound data in a file that uses a PowerPoint 4.0 native file format, leading to memory corruption, aka "Legacy File Format Vulnerability," a different vulnerability than CVE-2009-0222, CVE-2009-0223, CVE-2009-0227, and CVE-2009-1137.
Exploit prediction
34.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-017
vendor-advisory
-
secunia.com
/advisories/32428
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2009/1290
vdb-entry, vendor-advisory
-
securityfocus.com
/bid/34881
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6106
vdb-entry, signature
-
securitytracker.com
/id?1022205
vdb-entry
-
labs.idefense.com
/intelligence/vulnerabilities/display.php?id=789
third-party-advisory
-
us-cert.gov
/cas/techalerts/TA09-132A.html
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2009-0226
- NVD CVE-2009-0226
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.