WMI Object Broker Vulnerability
CVE-2006-4704 is a cross-zone scripting and remote code execution vulnerability in the WMI Object Broker ActiveX control used by the WMI Wizard in Microsoft Visual Studio 2005. Improper validation of instantiated controls allows objects created through the broker to bypass the ActiveX security model, including kill-bit and safe-for-scripting restrictions. A specially crafted web page can exploit this behavior to execute arbitrary code with the visiting user's privileges. The vulnerability was publicly disclosed and actively exploited when Microsoft issued MS06-073 in December 2006.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation executes arbitrary code with the local user's rights. If that user has administrative privileges, an attacker can take complete control of the system, install programs, view, modify or delete data, and create accounts with full user rights. Exploitation under a less-privileged account is constrained by that account's permissions.
If you can’t patch tonight, do this now.
Temporarily disable the WMI Object Broker control in Internet Explorer using its ActiveX kill bit, then restart the browser. This workaround may impair the Visual Studio 2005 WMI Wizard. Alternatively, disable ActiveX execution or require prompts in the Internet and Local intranet zones, or set these zones to High security. Internet Explorer 7 blocks this control by default unless it has been enabled through ActiveX opt-in or previously used in an earlier browser version. Windows Server 2003 Internet Explorer Enhanced Security Configuration reduces exposure outside the Trusted sites zone. These measures block known attack vectors but do not repair the underlying vulnerability.
Patch, then assume compromise.
Apply Microsoft security update KB925674, which changes how WMI Object Broker instantiates other controls. Update every installed copy of the affected component earlier than version 8.0.50727.236, including copies installed by other programs, and verify the installed component version afterward. Installation requires Visual Studio 2005 and Windows Installer 3.1; a restart may be necessary if affected files are in use.
1 exploit validated by Mallory's analysis.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.