Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2009-0323: Stack Buffer Overflow in W3C Amaya Web Browser 10.0/11.0

Published Jan 28, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS62.5%99th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
W3
IdentifiersCVE-2009-0323CWE-121

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
W3Amayaapplication
FAQ

Frequently asked questions

Is CVE-2009-0323 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-0323 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-0323?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2009-0323, the earliest disclosed Jan 28, 2009.
Is there a patch for CVE-2009-0323?
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.
What products are affected by CVE-2009-0323?
W3 Amaya.
How severe is CVE-2009-0323?
CVE-2009-0323 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 62.5% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.