Loading vulnerability…
Microsoft Internet Explorer 6 and Internet Explorer 7 Beta 2 contain a memory corruption condition reachable via a specific createTextRange call on a checkbox object. Triggering this condition results in dereferencing an invalid table pointer, leading to a crash (denial of service) and potentially enabling arbitrary code execution in the context of the current user when a victim visits a specially crafted web page.
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 (4 hidden).
This repository contains a single Metasploit module: 'ms06_013_createtextrange.rb', which exploits a code execution vulnerability (CVE-2006-1359) in Microsoft Internet Explorer 6 and 7 (Beta 2) on Windows XP SP2. The exploit works by serving a malicious HTML/JavaScript page to the victim's browser, using a heap spray technique to place shellcode in memory and then triggering the vulnerability via the createTextRange() method on a crafted input element. The module allows the attacker to deliver arbitrary Metasploit payloads (such as reverse shells) to the victim. The exploit is operational and customizable, but not weaponized for mass exploitation. The only network endpoint is the HTTP server provided by the Metasploit module, which serves the exploit page to the target browser. The repository is structured as a single Ruby file compatible with the Metasploit Framework.
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.