Loading vulnerability…
CVE-2009-0323 describes multiple stack-based buffer overflows in W3C Amaya Web Browser versions 10.0 and 11.0. The vulnerabilities are triggered by improper handling of input data in several functions: a long 'type' parameter in an input tag (EndOfXmlAttributeValue), a malformed 'HTML GI' in a start tag (ProcessStartGI), and unspecified vectors in html2thot.c and xml2thot.c involving the msgBuffer variable. These flaws allow remote attackers to execute arbitrary code by crafting malicious HTML/XML content.
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 (1 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/browser/amaya_bdo.rb) that exploits a stack buffer overflow vulnerability (CVE-2009-0323) in the Amaya Browser v11 for Windows. The exploit works by serving a specially crafted HTML page containing an overlong <bdo> tag attribute to the victim. When the vulnerable browser parses this page, a buffer overflow occurs, allowing the attacker to execute arbitrary code. The module leverages Metasploit's HTTP server to deliver the payload and supports customizable payloads up to 970 bytes, avoiding null bytes. The exploit targets users who visit the malicious page with the vulnerable browser. The code is operational and can be used to achieve code execution on affected systems.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.