ID CVE-2009-0323
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.
References
Vulnerable Configurations
  • cpe:2.3:a:w3:amaya:0.9
    cpe:2.3:a:w3:amaya:0.9
  • cpe:2.3:a:w3:amaya:0.95b
    cpe:2.3:a:w3:amaya:0.95b
  • cpe:2.3:a:w3:amaya:1.0
    cpe:2.3:a:w3:amaya:1.0
  • cpe:2.3:a:w3:amaya:1.0a
    cpe:2.3:a:w3:amaya:1.0a
  • cpe:2.3:a:w3:amaya:1.1
    cpe:2.3:a:w3:amaya:1.1
  • cpe:2.3:a:w3:amaya:1.1a
    cpe:2.3:a:w3:amaya:1.1a
  • cpe:2.3:a:w3:amaya:1.1c
    cpe:2.3:a:w3:amaya:1.1c
  • cpe:2.3:a:w3:amaya:1.2
    cpe:2.3:a:w3:amaya:1.2
  • cpe:2.3:a:w3:amaya:1.2a
    cpe:2.3:a:w3:amaya:1.2a
  • cpe:2.3:a:w3:amaya:1.3
    cpe:2.3:a:w3:amaya:1.3
  • cpe:2.3:a:w3:amaya:1.3a
    cpe:2.3:a:w3:amaya:1.3a
  • cpe:2.3:a:w3:amaya:1.3b
    cpe:2.3:a:w3:amaya:1.3b
  • cpe:2.3:a:w3:amaya:1.4
    cpe:2.3:a:w3:amaya:1.4
  • cpe:2.3:a:w3:amaya:1.4a
    cpe:2.3:a:w3:amaya:1.4a
  • cpe:2.3:a:w3:amaya:2.0
    cpe:2.3:a:w3:amaya:2.0
  • cpe:2.3:a:w3:amaya:2.1
    cpe:2.3:a:w3:amaya:2.1
  • cpe:2.3:a:w3:amaya:2.2
    cpe:2.3:a:w3:amaya:2.2
  • cpe:2.3:a:w3:amaya:2.3
    cpe:2.3:a:w3:amaya:2.3
  • cpe:2.3:a:w3:amaya:2.4
    cpe:2.3:a:w3:amaya:2.4
  • cpe:2.3:a:w3:amaya:3.0
    cpe:2.3:a:w3:amaya:3.0
  • cpe:2.3:a:w3:amaya:3.1
    cpe:2.3:a:w3:amaya:3.1
  • cpe:2.3:a:w3:amaya:3.2
    cpe:2.3:a:w3:amaya:3.2
  • cpe:2.3:a:w3:amaya:3.2.1
    cpe:2.3:a:w3:amaya:3.2.1
  • cpe:2.3:a:w3:amaya:4.0
    cpe:2.3:a:w3:amaya:4.0
  • cpe:2.3:a:w3:amaya:4.1
    cpe:2.3:a:w3:amaya:4.1
  • cpe:2.3:a:w3:amaya:4.2
    cpe:2.3:a:w3:amaya:4.2
  • cpe:2.3:a:w3:amaya:4.2.1
    cpe:2.3:a:w3:amaya:4.2.1
  • cpe:2.3:a:w3:amaya:4.3
    cpe:2.3:a:w3:amaya:4.3
  • cpe:2.3:a:w3:amaya:4.3.1
    cpe:2.3:a:w3:amaya:4.3.1
  • cpe:2.3:a:w3:amaya:4.3.2
    cpe:2.3:a:w3:amaya:4.3.2
  • cpe:2.3:a:w3:amaya:5.0
    cpe:2.3:a:w3:amaya:5.0
  • cpe:2.3:a:w3:amaya:5.1
    cpe:2.3:a:w3:amaya:5.1
  • cpe:2.3:a:w3:amaya:5.2
    cpe:2.3:a:w3:amaya:5.2
  • cpe:2.3:a:w3:amaya:5.3
    cpe:2.3:a:w3:amaya:5.3
  • cpe:2.3:a:w3:amaya:6.0
    cpe:2.3:a:w3:amaya:6.0
  • cpe:2.3:a:w3:amaya:6.1
    cpe:2.3:a:w3:amaya:6.1
  • cpe:2.3:a:w3:amaya:6.2
    cpe:2.3:a:w3:amaya:6.2
  • cpe:2.3:a:w3:amaya:6.3
    cpe:2.3:a:w3:amaya:6.3
  • cpe:2.3:a:w3:amaya:6.4
    cpe:2.3:a:w3:amaya:6.4
  • cpe:2.3:a:w3:amaya:7.0
    cpe:2.3:a:w3:amaya:7.0
  • cpe:2.3:a:w3:amaya:7.1
    cpe:2.3:a:w3:amaya:7.1
  • cpe:2.3:a:w3:amaya:7.2
    cpe:2.3:a:w3:amaya:7.2
  • cpe:2.3:a:w3:amaya:8.0
    cpe:2.3:a:w3:amaya:8.0
  • cpe:2.3:a:w3:amaya:8.1
    cpe:2.3:a:w3:amaya:8.1
  • cpe:2.3:a:w3:amaya:8.1a
    cpe:2.3:a:w3:amaya:8.1a
  • cpe:2.3:a:w3:amaya:8.1b
    cpe:2.3:a:w3:amaya:8.1b
  • cpe:2.3:a:w3:amaya:8.2
    cpe:2.3:a:w3:amaya:8.2
  • cpe:2.3:a:w3:amaya:8.3
    cpe:2.3:a:w3:amaya:8.3
  • cpe:2.3:a:w3:amaya:8.4
    cpe:2.3:a:w3:amaya:8.4
  • cpe:2.3:a:w3:amaya:8.5
    cpe:2.3:a:w3:amaya:8.5
  • cpe:2.3:a:w3:amaya:8.6
    cpe:2.3:a:w3:amaya:8.6
  • cpe:2.3:a:w3:amaya:8.7
    cpe:2.3:a:w3:amaya:8.7
  • cpe:2.3:a:w3:amaya:8.7.1
    cpe:2.3:a:w3:amaya:8.7.1
  • cpe:2.3:a:w3:amaya:8.7.2
    cpe:2.3:a:w3:amaya:8.7.2
  • cpe:2.3:a:w3:amaya:8.8.1
    cpe:2.3:a:w3:amaya:8.8.1
  • cpe:2.3:a:w3:amaya:8.8.3
    cpe:2.3:a:w3:amaya:8.8.3
  • cpe:2.3:a:w3:amaya:8.8.4
    cpe:2.3:a:w3:amaya:8.8.4
  • cpe:2.3:a:w3:amaya:8.8.5
    cpe:2.3:a:w3:amaya:8.8.5
  • cpe:2.3:a:w3:amaya:8.52
    cpe:2.3:a:w3:amaya:8.52
  • cpe:2.3:a:w3:amaya:9.0
    cpe:2.3:a:w3:amaya:9.0
  • cpe:2.3:a:w3:amaya:9.1
    cpe:2.3:a:w3:amaya:9.1
  • cpe:2.3:a:w3:amaya:9.2.1
    cpe:2.3:a:w3:amaya:9.2.1
  • cpe:2.3:a:w3:amaya:9.3
    cpe:2.3:a:w3:amaya:9.3
  • cpe:2.3:a:w3:amaya:9.4
    cpe:2.3:a:w3:amaya:9.4
  • cpe:2.3:a:w3:amaya:9.5
    cpe:2.3:a:w3:amaya:9.5
  • cpe:2.3:a:w3:amaya:9.52
    cpe:2.3:a:w3:amaya:9.52
  • cpe:2.3:a:w3:amaya:9.53
    cpe:2.3:a:w3:amaya:9.53
  • cpe:2.3:a:w3:amaya:9.54
    cpe:2.3:a:w3:amaya:9.54
  • cpe:2.3:a:w3:amaya:9.55
    cpe:2.3:a:w3:amaya:9.55
  • cpe:2.3:a:w3:amaya:10.0
    cpe:2.3:a:w3:amaya:10.0
  • cpe:2.3:a:w3:amaya:11.0
    cpe:2.3:a:w3:amaya:11.0
CVSS
Base: 10.0 (as of 29-01-2009 - 12:08)
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
exploit-db via4
  • description Amaya Web Editor XML and HTML parser Vulnerabilities. CVE-2009-0323. Dos exploit for windows platform
    file exploits/windows/dos/7902.txt
    id EDB-ID:7902
    last seen 2016-02-01
    modified 2009-01-28
    platform windows
    port
    published 2009-01-28
    reporter Core Security
    source https://www.exploit-db.com/download/7902/
    title Amaya Web Editor XML and HTML parser Vulnerabilities
    type dos
  • description Amaya Browser v11.0 bdo tag overflow. CVE-2009-0323. Remote exploit for windows platform
    id EDB-ID:16548
    last seen 2016-02-02
    modified 2010-05-09
    published 2010-05-09
    reporter metasploit
    source https://www.exploit-db.com/download/16548/
    title Amaya Browser 11.0 - bdo tag Overflow
metasploit via4
description This module exploits a stack buffer overflow in the Amaya v11 Browser. By sending an overly long string to the "bdo" tag, an attacker may be able to execute arbitrary code.
id MSF:EXPLOIT/WINDOWS/BROWSER/AMAYA_BDO
last seen 2019-03-30
modified 2017-07-24
published 2009-10-10
reliability Normal
reporter Rapid7
source https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/windows/browser/amaya_bdo.rb
title Amaya Browser v11.0 'bdo' Tag Overflow
nessus via4
NASL family FreeBSD Local Security Checks
NASL id FREEBSD_PKG_A89B76A7F6BD11DD94D90030843D3802.NASL
description Secunia reports : A boundary error when processing 'div' HTML tags can be exploited to cause a stack-based buffer overflow via an overly long 'id' parameter. A boundary error exists when processing overly long links. This can be exploited to cause a stack-based buffer overflow by tricking the user into e.g. editing a malicious link. A boundary error when processing e.g. a 'bdo' HTML tag having an overly long 'dir' attribute can be exploited to cause a stack-based buffer overflow. A boundary error when processing 'input' HTML tags can be exploited to cause a stack-based buffer overflow via an overly long e.g. 'type' attribute.
last seen 2019-02-21
modified 2018-02-15
plugin id 56495
published 2011-10-14
reporter Tenable
source https://www.tenable.com/plugins/index.php?view=single&id=56495
title FreeBSD : amaya -- multiple buffer overflow vulnerabilities (a89b76a7-f6bd-11dd-94d9-0030843d3802)
packetstorm via4
data source https://packetstormsecurity.com/files/download/83102/amaya_bdo.rb.txt
id PACKETSTORM:83102
last seen 2016-12-05
published 2009-11-26
reporter Rob Carter
source https://packetstormsecurity.com/files/83102/Amaya-Browser-v11.0-bdo-tag-overflow.html
title Amaya Browser v11.0 bdo tag overflow
refmap via4
bugtraq 20090128 CORE-2008-1211: Amaya web editor XML and HTML parser vulnerabilities
exploit-db 7902
misc http://www.coresecurity.com/content/amaya-buffer-overflows
xf amaya-html-tags-bo(48325)
Last major update 10-02-2009 - 02:00
Published 28-01-2009 - 15:30
Last modified 11-10-2018 - 17:01
Back to Top