CVE-2006-3864 in the critical feed json
Unspecified vulnerability in mso.dll in Microsoft Office 2000, XP, and 2003, and Microsoft PowerPoint 2000, XP, and 2003, allows remote use…
published 2006-10-10 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-3858
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 33.8%
- EPSS 33.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in mso.dll in Microsoft Office 2000, XP, and 2003, and Microsoft PowerPoint 2000, XP, and 2003, allows remote user-assisted attackers to execute arbitrary code via a malformed record in a (1) .DOC, (2) .PPT, or (3) .XLS file that triggers memory corruption, related to an "array boundary condition" (possibly an array index overflow), a different vulnerability than CVE-2006-3434, CVE-2006-3650, and CVE-2006-3868.
Exploit prediction
33.85% 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-062
vendor-advisory
-
support.microsoft.com
/kb/922581
vendor-advisory
-
vupen.com
/english/advisories/2006/3981
vdb-entry, vendor-advisory
-
secunia.com
/advisories/22339
third-party-advisory, vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A632
vdb-entry, signature
-
osvdb.org
/29429
vdb-entry
-
kb.cert.org
/vuls/id/176556
third-party-advisory, us-government-resource
- secway.org /advisory/AD20061010.txt
-
securityfocus.com
/bid/20384
vdb-entry
-
securitytracker.com
/id?1017034
vdb-entry
-
securityfocus.com
/archive/1/448268/100/0/threaded
mailing-list
Sources
- CVE List CVE-2006-3864
- NVD CVE-2006-3864
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.