CVE Vulnerabilities


Use After Free

Published: Jul 15, 2015 | Modified: Sep 08, 2021
CVSS 3.x
CVSS 2.x

Use-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.15 and 11.x before 11.0.12, Acrobat and Acrobat Reader DC Classic before 2015.006.30060, and Acrobat and Acrobat Reader DC Continuous before 2015.008.20082 on Windows and OS X allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-4448, CVE-2015-5099, CVE-2015-5101, CVE-2015-5111, CVE-2015-5113, and CVE-2015-5114.


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 10.0 (including) 10.1.15 (excluding)
Acrobat Adobe 11.0.0 (including) 11.0.12 (excluding)
Acrobat_dc Adobe 15.006.30033 (including) 15.006.30060 (excluding)
Acrobat_dc Adobe 15.007.20033 (including) 15.008.20082 (excluding)
Acrobat_reader Adobe 10.0 (including) 10.1.15 (excluding)
Acrobat_reader Adobe 11.0.0 (including) 11.0.12 (excluding)
Acrobat_reader_dc Adobe 15.006.30033 (including) 15.006.30060 (excluding)
Acrobat_reader_dc Adobe 15.007.20033 (including) 15.008.20082 (excluding)

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