CVE-2010-0252 in the critical feed json
The Microsoft Data Analyzer ActiveX control (aka the Office Excel ActiveX control for Data Analysis) in max3activex.dll in Microsoft Window…
published 16y ago modified 4mo ago also EUVD-2010-0283
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 28.8%
- EPSS 28.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
The Microsoft Data Analyzer ActiveX control (aka the Office Excel ActiveX control for Data Analysis) in max3activex.dll in Microsoft Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 allows remote attackers to execute arbitrary code via a crafted web page that corrupts the "system state," aka "Microsoft Data Analyzer ActiveX Control Vulnerability."
Is CVE-2010-0252 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 FencerExploit prediction
28.76% 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-94 Improper Control of Generation of Code
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2010/ms10-008
vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2010/ms10-034
vendor-advisory
-
secunia.com
/advisories/38503
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/40059
third-party-advisory
-
us-cert.gov
/cas/techalerts/TA10-040A.html
third-party-advisory, us-government-resource
-
us-cert.gov
/cas/techalerts/TA10-159B.html
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A8424
vdb-entry, signature
Sources
- CVE List CVE-2010-0252
- NVD CVE-2010-0252
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.