CVE Vulnerabilities

CVE-2011-3659

Use After Free

Published: Feb 01, 2012 | Modified: Nov 21, 2024
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
9.3 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C
RedHat/V2
6.8 CRITICAL
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V3
Ubuntu
MEDIUM

Use-after-free vulnerability in Mozilla Firefox before 3.6.26 and 4.x through 9.0, Thunderbird before 3.1.18 and 5.0 through 9.0, and SeaMonkey before 2.7 might allow remote attackers to execute arbitrary code via vectors related to incorrect AttributeChildRemoved notifications that affect access to removed nsDOMAttribute child nodes.

Weakness

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

Affected Software

Name Vendor Start Version End Version
Firefox Mozilla * 3.6.26 (excluding)
Firefox Mozilla 4.0 (including) 10.0 (excluding)
Seamonkey Mozilla * 2.7 (excluding)
Thunderbird Mozilla * 3.1.18 (excluding)
Thunderbird Mozilla 5.0 (including) 10.0 (excluding)
Red Hat Enterprise Linux 4 RedHat firefox-0:3.6.26-2.el4 *
Red Hat Enterprise Linux 5 RedHat firefox-0:3.6.26-1.el5_7 *
Red Hat Enterprise Linux 5 RedHat xulrunner-0:1.9.2.26-1.el5_7 *
Red Hat Enterprise Linux 6 RedHat firefox-0:3.6.26-1.el6_2 *
Red Hat Enterprise Linux 6 RedHat xulrunner-0:1.9.2.26-1.el6_2 *
Red Hat Enterprise Linux 6 RedHat thunderbird-0:3.1.18-1.el6_2 *
Firefox Ubuntu hardy *
Firefox Ubuntu lucid *
Firefox Ubuntu maverick *
Firefox Ubuntu natty *
Firefox Ubuntu oneiric *
Seamonkey Ubuntu hardy *
Seamonkey Ubuntu lucid *
Seamonkey Ubuntu maverick *
Seamonkey Ubuntu natty *
Seamonkey Ubuntu oneiric *
Thunderbird Ubuntu hardy *
Thunderbird Ubuntu lucid *
Thunderbird Ubuntu maverick *
Thunderbird Ubuntu natty *
Thunderbird Ubuntu oneiric *
Xulrunner-1.9.2 Ubuntu hardy *
Xulrunner-1.9.2 Ubuntu lucid *
Xulrunner-1.9.2 Ubuntu maverick *
Xulrunner-1.9.2 Ubuntu natty *
Xulrunner-2.0 Ubuntu natty *

Extended Description

The use of previously-freed memory can have any number of adverse consequences, ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw. The simplest way data corruption may occur involves the system’s reuse of the freed memory. Use-after-free errors have two common and sometimes overlapping causes:

In this scenario, the memory in question is allocated to another pointer validly at some point after it has been freed. The original pointer to the freed memory is used again and points to somewhere within the new allocation. As the data is changed, it corrupts the validly used memory; this induces undefined behavior in the process. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Potential Mitigations

References