CVE-2006-3435 in the critical feed json
PowerPoint in Microsoft Office 2000, XP, 2003, 2004 for Mac, and v.X for Mac does not properly parse the slide notes field in a document, w…
published 2006-10-10 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-3431
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 37.3%
- EPSS 37.3% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
PowerPoint in Microsoft Office 2000, XP, 2003, 2004 for Mac, and v.X for Mac does not properly parse the slide notes field in a document, which allows remote user-assisted attackers to execute arbitrary code via crafted data in this field, which triggers an erroneous object pointer calculation that uses data from within the document. NOTE: this issue is different than other PowerPoint vulnerabilities including CVE-2006-4694.
Exploit prediction
37.26% 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
-
securityfocus.com
/archive/1/449179/100/0/threaded
vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2006/ms06-058
vendor-advisory
-
vupen.com
/english/advisories/2006/3977
vdb-entry, vendor-advisory
-
kb.cert.org
/vuls/id/187028
third-party-advisory, us-government-resource
- zerodayinitiative.com /advisories/ZDI-06-032.html
-
osvdb.org
/29446
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A476
vdb-entry, signature
-
securityfocus.com
/archive/1/448149/100/0/threaded
mailing-list
-
securityfocus.com
/bid/20304
vdb-entry
-
securitytracker.com
/id?1017030
vdb-entry
Sources
- CVE List CVE-2006-3435
- NVD CVE-2006-3435
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.