CVE-2010-4588 in the critical feed json
The WBEMSingleView.ocx ActiveX control 1.50.1131.0 in Microsoft WMI Administrative Tools 1.1 and earlier allows remote attackers to execute…
published 15y ago modified 4mo ago also EUVD-2010-4554
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 32.3%
- EPSS 32.3% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
The WBEMSingleView.ocx ActiveX control 1.50.1131.0 in Microsoft WMI Administrative Tools 1.1 and earlier allows remote attackers to execute arbitrary code via a crafted argument to the ReleaseContext method, a different vector than CVE-2010-3973, possibly an untrusted pointer dereference.
Is CVE-2010-4588 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 (EDB-15809)
- Published
Exploit prediction
32.28% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15809 Microsoft WMITools - ActiveX Remote Command Execution remote, 2010-12-22
- wooyun.org http://www.wooyun.org/bug.php?action=view&id=1006 referenced PoC, tagged "exploit" by a source, unverified
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
-
wooyun.org
/bug.php?action=view&id=1006
exploit
-
secunia.com
/advisories/42693
third-party-advisory, vendor-advisory
- blogs.technet.com /b/srd/archive/2011/01/07/assessing-the-risk-of-public-issues-currently-being-tracked-by-the-msrc.aspx
-
kb.cert.org
/vuls/id/725596
third-party-advisory, us-government-resource
- twitter.com /carsteneiram/status/17526155733110784
Sources
- CVE List CVE-2010-4588
- NVD CVE-2010-4588
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.