CVE-2011-0656 in the critical feed json
Microsoft PowerPoint 2002 SP3, 2003 SP3, 2007 SP2, and 2010; Office 2004, 2008, and 2011 for Mac; Open XML File Format Converter for Mac; O…
published 2011-04-13 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0674
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 29.6%
- EPSS 29.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Microsoft PowerPoint 2002 SP3, 2003 SP3, 2007 SP2, and 2010; Office 2004, 2008, and 2011 for Mac; Open XML File Format Converter for Mac; Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP2; PowerPoint Viewer; PowerPoint Viewer 2007 SP2; and PowerPoint Web App do not properly validate PersistDirectoryEntry records in PowerPoint documents, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a Slide with a malformed record, which triggers an exception and later use of an unspecified method, aka "Persist Directory RCE Vulnerability."
Exploit prediction
29.60% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
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-20 Improper Input Validation
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2011/ms11-022
vendor-advisory
-
vupen.com
/english/advisories/2011/0941
vdb-entry, vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11761
vdb-entry, signature
-
us-cert.gov
/cas/techalerts/TA11-102A.html
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1025340
vdb-entry
- zerodayinitiative.com /advisories/ZDI-11-125
-
securityfocus.com
/bid/47251
vdb-entry
-
osvdb.org
/71770
vdb-entry
-
securityfocus.com
/archive/1/517482/100/0/threaded
mailing-list
Sources
- CVE List CVE-2011-0656
- NVD CVE-2011-0656
Fencer Intel 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.