Stack Buffer Overflow in W3C Amaya Web Browser 10.0/11.0
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote attackers to execute arbitrary code in the context of the user running Amaya, potentially leading to full system compromise if the user has sufficient privileges. The vulnerabilities are exploitable via crafted web content, making drive-by attacks feasible.
If you can’t patch tonight, do this now.
Until a patch is available, restrict Amaya's use to trusted local files and avoid browsing untrusted or unknown web content. Employ host-based intrusion prevention systems and consider running Amaya with reduced privileges to limit the impact of exploitation.
Patch, then assume compromise.
Upgrade to a patched version of Amaya, if available, that addresses these buffer overflow vulnerabilities. If no patch is available, consider discontinuing use of Amaya or restricting its use to trusted content only.
1 exploit validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.