Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

MSCOMCTL.OCX ListView/TreeView ActiveX Remote Code Execution

IdentifiersCVE-2012-0158CWE-119Also known asms12_027

CVE-2012-0158 is a remote code execution vulnerability in the MSCOMCTL.OCX Microsoft Windows Common Controls ActiveX library, specifically affecting the ListView, ListView2, TreeView, and TreeView2 controls. The flaw affects Microsoft Office 2003 SP3, 2007 SP2/SP3, and 2010 Gold/SP1, as well as other Microsoft products that ship or use the vulnerable control, including Office 2003 Web Components SP3, multiple SQL Server versions, BizTalk Server 2002 SP1, Commerce Server versions, Visual FoxPro 8.0 SP1/9.0 SP2, and the Visual Basic 6.0 runtime. Microsoft described exploitation as causing "system state" corruption, and multiple sources characterize the issue as a buffer overflow/memory corruption condition in the ListView/TreeView ActiveX controls. An attacker can trigger the flaw by convincing a victim to open a crafted Office document or RTF file, or by serving malicious content via a crafted website that instantiates the vulnerable control. Successful exploitation allows arbitrary code execution in the context of the user opening the malicious content. The vulnerability was widely exploited in the wild beginning in 2012 and became one of the most commonly used Office exploit primitives in targeted intrusion and crimeware campaigns.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in arbitrary code execution on the victim system in the security context of the current user. In practical campaigns, this has been used to drop and execute first-stage malware, download additional payloads, install RATs and espionage implants, and establish persistence for follow-on intrusion activity. Because the bug is commonly delivered through spear-phishing documents and RTF files, it has been heavily used for initial access against governments, NGOs, journalists, activists, military targets, and enterprises. Impact depends on user privileges; if the victim has elevated rights, the attacker may gain broader control of the host and use it as a foothold for lateral movement, credential theft, surveillance, and data exfiltration.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by blocking or tightly controlling delivery vectors commonly used for exploitation: prevent opening of untrusted Office and RTF attachments, disable or restrict ActiveX where operationally feasible, use Protected View and attachment sandboxing, and filter spear-phishing emails carrying Office/RTF content. Restrict access to malicious or untrusted websites that could host exploit content. Use application allowlisting, EDR, and network controls to detect or block post-exploitation payload execution. Because this vulnerability has been extensively used in phishing campaigns, user-focused controls around attachment handling and email security materially reduce risk, but patching remains the primary mitigation.

Remediation

Patch, then assume compromise.

Apply Microsoft's security update for MS12-027 and upgrade all affected Microsoft products to supported, fully patched versions. Replace or retire end-of-life software that still includes vulnerable MSCOMCTL.OCX components, including legacy Office, Visual Basic 6.0 runtime-dependent applications, and unsupported server products. Verify that vulnerable copies of MSCOMCTL.OCX are updated across all installed Microsoft software, not just Office, because the control is shared by multiple products. Where possible, migrate users away from legacy Office versions and unsupported Windows-era application stacks that continue to expose this control.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationBiztalk Serverapplication
Microsoft CorporationCommerce Serverapplication
Microsoft CorporationCommerce Server 2009application
Microsoft CorporationOfficeapplication
Microsoft CorporationOffice Web Componentsapplication
Microsoft CorporationSql Server 2000application
Microsoft CorporationSql Server 2005application
Microsoft CorporationSql Server 2008application
Microsoft CorporationVisual Basicapplication
Microsoft CorporationVisual Foxproapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence38

Every observed campaign linking this CVE to a named adversary.

Associated malware38

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.