cve.bz

CVE-2012-0158 Microsoft MSCOMCTL.OCX Remote Code Execution Vulnerability

8.8 highKEVExploitEPSS >99.9%Fix available

High (8.8) in Microsoft MSCOMCTL.OCX. In CISA KEV since 2021-11-03, with known ransomware use. EPSS >99.9% estimated probability of exploitation activity in the next 30 days.

On this page
The (1) ListView, (2) ListView2, (3) TreeView, and (4) TreeView2 ActiveX controls in MSCOMCTL.OCX in the Common Controls in Microsoft Office 2003 SP3, 2007 SP2 and SP3, and 2010 Gold and SP1; Office 2003 Web Components SP3; SQL Server 2000 SP4, 2005 SP4, and 2008 SP2, SP3, and R2; BizTalk Server 2002 SP1; Commerce Server 2002 SP4, 2007 SP2, and 2009 Gold and R2; Visual FoxPro 8.0 SP1 and 9.0 SP2; and Visual Basic 6.0 Runtime allow remote attackers to execute arbitrary code via a crafted (a) web site, (b) Office document, or (c) .rtf file that triggers "system state" corruption, as exploited in the wild in April 2012, aka "MSCOMCTL.OCX RCE Vulnerability."

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
>99.9% (unchanged from >99.9% a week ago; >99.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2021-11-03, due 2022-05-03, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2012-0158 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2012-0158?via=ask-ai-copy and https://cve.bz/cve/CVE-2012-0158?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2012-0158 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
microsoft:office2003:sp3
microsoft:office2007:sp2
microsoft:office2007:sp3
microsoft:office2010
microsoft:office2010:sp1
microsoft:office_web_components2003:sp3
microsoft:sql_server_2008r2
microsoft:sql_server_2008r2:sp1
microsoft:biztalk_server2002:sp1
microsoft:commerce_server2002:sp4
microsoft:commerce_server2007:sp2
microsoft:commerce_server_2009r2
microsoft:visual_basic6.0
microsoft:visual_foxpro8.0:sp1
microsoft:visual_foxpro9.0:sp2

Public exploits

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET WEB_CLIENT Microsoft Rich Text File download with vulnerable ActiveX control flowbit set 1 sid 2025082
  • Emerging Threats Open ET WEB_CLIENT Microsoft Rich Text File download with vulnerable ActiveX control flowbit set 2 sid 2025083
  • Emerging Threats Open ET WEB_CLIENT Microsoft Rich Text File download with vulnerable ActiveX control flowbit set 3 sid 2025084

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON