CVE-2009-0323 in the critical feed json
Multiple stack-based buffer overflows in W3C Amaya Web Browser 10.0 and 11.0 allow remote attackers to execute arbitrary code via (1) a lon…
published 2009-01-28 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0327
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 62.5%
- EPSS 62.5% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
Multiple stack-based buffer overflows in W3C Amaya Web Browser 10.0 and 11.0 allow remote attackers to execute arbitrary code via (1) a long type parameter in an input tag, which is not properly handled by the EndOfXmlAttributeValue function; (2) an "HTML GI" in a start tag, which is not properly handled by the ProcessStartGI function; and unspecified vectors in (3) html2thot.c and (4) xml2thot.c, related to the msgBuffer variable. NOTE: these are different vectors than CVE-2008-6005.
Timeline
- First public exploit (Metasploit exploit/windows/browser/amaya_bdo)
- Published
Exploit prediction
62.49% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/browser/amaya_bdo Amaya Browser v11.0 'bdo' Tag Overflow metasploit exploit, normal rank, 2009-01-28
- EDB-16548 Amaya Browser 11.0 - bdo tag Overflow (Metasploit) remote, 2010-05-09
- EDB-7902 Amaya Web Editor 11.0 - XML / HTML Parser dos, 2009-01-28
- coresecurity.com http://www.coresecurity.com/content/amaya-buffer-overflows referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
Sources
- CVE List CVE-2009-0323
- NVD CVE-2009-0323
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.