Loading vulnerability…
CVE-2013-1690 is a memory-safety vulnerability in Mozilla Firefox, Firefox ESR, Thunderbird, Thunderbird ESR, and SeaMonkey. Improper handling of onreadystatechange events in conjunction with page reloads can cause execution to reach an unmapped memory location. Specially crafted web content can trigger an application crash and may permit 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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module targeting a use-after-free vulnerability (CVE-2013-1690) in Mozilla Firefox 17 and 21 on Windows XP SP3. The exploit is delivered via a malicious HTTP server that serves specially crafted HTML and JavaScript to the victim's browser. The JavaScript performs a heap spray and triggers the vulnerability using the 'onreadystatechange' event and 'window.stop()' API, leading to arbitrary code execution via a ROP chain. The module checks the User-Agent to ensure the target is Windows XP with a vulnerable Firefox version before serving the exploit. The payload is customizable and delivered as part of the heap spray, allowing for various post-exploitation actions. The main entry point is the Ruby file implementing the Metasploit module, which dynamically generates the malicious HTML and JavaScript. The only fingerprintable endpoint is '/iframe.html', which serves the exploit's iframe content.
This repository contains a browser-based exploit targeting Mozilla Firefox, likely version 17, as indicated by version checks in the JavaScript code. The exploit is structured as a multi-stage attack using several HTML/JavaScript files (content_1.html, content_2.html, content_3.html). The main entry point is content_1.html, which initializes several large arrays and ArrayBuffers to set up memory conditions for exploitation. The code attempts to leak information and then trigger a use-after-free (UAF) vulnerability by manipulating DOM elements and iframe navigation. A large shellcode payload is embedded as a Unicode string in the JavaScript and is intended to be executed after successful exploitation, potentially leading to arbitrary code execution in the browser context. The exploit is a proof-of-concept and requires the victim to visit a malicious web page. No external network endpoints are used; all files are local to the exploit. The repository demonstrates advanced browser exploitation techniques, including heap spraying, information leakage, and UAF triggering.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability included in the Kore exploit kit according to the table.
A vulnerability affecting Firefox and Thunderbird involving onreadystatechange event handling during page reloading, used in this campaign to execute shellcode and deliver malware.
A critical memory corruption issue in Mozilla products where specially crafted web content using the onreadystatechange event and page reloads could trigger execution of unmapped memory, leading to a potentially exploitable crash.
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.