CVE-2009-2477 is a memory-safety vulnerability in js/src/jstracer.cpp in Mozilla Firefox 3.5 prior to 3.5.1, specifically in the TraceMonkey just-in-time JavaScript compiler. The flaw is triggered through certain use of the JavaScript escape function and results in access to uninitialized memory locations. The issue was originally demonstrated using a crafted document containing P and FONT elements. A remote attacker can deliver malicious web content that causes the JIT engine to operate on uninitialized memory, leading to memory corruption conditions that can be leveraged for arbitrary code execution in the context of the browser process.
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 (3 hidden).
This repository contains a single Metasploit module (modules/exploits/multi/browser/firefox_escape_retval.rb) that exploits a memory corruption vulnerability (CVE-2009-2477) in Mozilla Firefox 3.5.0. The exploit is triggered when a victim visits a malicious web page served by the module's built-in HTTP server. The module uses JavaScript heap spraying to deliver a customizable Metasploit payload, exploiting improper handling of the escape() function's return value in Firefox's JavaScript engine. The exploit targets both Windows XP and Mac OS X 10.5.7 (Intel) platforms. The code is operational and allows for arbitrary code execution in the context of the browser process. The repository is structured as a typical Metasploit exploit module, with Ruby code orchestrating the attack and generating the malicious HTML/JavaScript payload on the fly.
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.
2 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.