Loading vulnerability…
A memory corruption vulnerability exists in Microsoft Internet Explorer 6 and 7 due to improper handling of objects in memory that are either uninitialized or deleted. The vulnerability can be triggered via a crafted web page that uses the getElementsByTagName method for the STYLE tag, selects the single element in the returned list, and modifies its outerHTML property. This flaw is related to the handling of Cascading Style Sheets (CSS) in mshtml.dll and can result in memory corruption, leading to arbitrary code execution.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (ms09_072_style_object.rb) that exploits a memory corruption vulnerability (CVE-2009-3672) in the getElementsByTagName function of Microsoft Internet Explorer 6 and 7 on Windows platforms. The exploit works by serving a specially crafted HTML page with embedded JavaScript to the victim's browser. The JavaScript performs a heap spray with attacker-controlled shellcode and triggers the vulnerability via manipulation of a STYLE element, leading to arbitrary code execution. The module is operational and allows the attacker to deliver any Metasploit-compatible payload. The only fingerprintable endpoint is the HTTP server that serves the malicious page. The code is structured as a standard Metasploit exploit module, with the main logic in the on_request_uri method, which handles incoming HTTP requests and delivers the exploit. The repository is focused and contains only the exploit module file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.