CVE-2010-0033 in the critical feed json
Stack-based buffer overflow in Microsoft Office PowerPoint 2003 SP3 allows remote attackers to execute arbitrary code via a crafted PowerPo…
published 16y ago modified 4mo ago also EUVD-2010-0065
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 51.1%
- EPSS 51.1% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
Stack-based buffer overflow in Microsoft Office PowerPoint 2003 SP3 allows remote attackers to execute arbitrary code via a crafted PowerPoint document, aka "PowerPoint Viewer TextBytesAtom Record Stack Overflow Vulnerability."
Is CVE-2010-0033 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/windows/fileformat/ms10_004_textbytesatom)
- Published
Exploit prediction
51.07% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/fileformat/ms10_004_textbytesatom MS10-004 Microsoft PowerPoint Viewer TextBytesAtom Stack Buffer Overflow metasploit exploit, good rank, 2010-02-09
- EDB-16665 Microsoft PowerPoint Viewer - TextBytesAtom Stack Buffer Overflow (MS10-004) (Metasploit) local, 2010-09-25
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/2010/ms10-004
vendor-advisory
-
us-cert.gov
/cas/techalerts/TA10-040A.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A7711
vdb-entry, signature
-
securitytracker.com
/id?1023563
vdb-entry
Sources
- CVE List CVE-2010-0033
- NVD CVE-2010-0033
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.