CVE Vulnerabilities

CVE-2009-4324

Use After Free

Published: Dec 15, 2009 | Modified: Dec 19, 2024
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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
LOW

Use-after-free vulnerability in the Doc.media.newPlayer method in Multimedia.api in Adobe Reader and Acrobat 9.x before 9.3, and 8.x before 8.2 on Windows and Mac OS X, allows remote attackers to execute arbitrary code via a crafted PDF file using ZLib compressed streams, as exploited in the wild in December 2009.

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
Acrobat Adobe 8.0 (including) 8.2 (excluding)
Acrobat Adobe 9.0 (including) 9.3 (excluding)
Acrobat_reader Adobe 8.0 (including) 8.2 (excluding)
Acrobat_reader Adobe 9.0 (including) 9.3 (excluding)
Extras for RHEL 3 RedHat acroread-0:9.3-3 *
Extras for RHEL 4 RedHat acroread-0:9.3-1.el4 *
Supplementary for Red Hat Enterprise Linux 5 RedHat acroread-0:9.3-1.el5 *
Acroread Ubuntu dapper *
Acroread Ubuntu devel *
Acroread Ubuntu hardy *
Acroread Ubuntu intrepid *
Acroread Ubuntu jaunty *
Acroread Ubuntu karmic *

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