CVE Vulnerabilities

CVE-2015-2301

Use After Free

Published: Mar 30, 2015 | Modified: Nov 07, 2023
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
2.6 LOW
AV:N/AC:H/Au:N/C:P/I:N/A:N
RedHat/V3
Ubuntu
MEDIUM

Use-after-free vulnerability in the phar_rename_archive function in phar_object.c in PHP before 5.5.22 and 5.6.x before 5.6.6 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger an attempted renaming of a Phar archive to the name of an existing file.

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
Ubuntu_linux Canonical 10.04 (including) 10.04 (including)
Ubuntu_linux Canonical 12.04 (including) 12.04 (including)
Ubuntu_linux Canonical 14.04 (including) 14.04 (including)
Ubuntu_linux Canonical 14.10 (including) 14.10 (including)
Debian_linux Debian 7.0 (including) 7.0 (including)
Opensuse Opensuse 13.1 (including) 13.1 (including)
Opensuse Opensuse 13.2 (including) 13.2 (including)
Red Hat Enterprise Linux 6 RedHat php-0:5.3.3-46.el6_6 *
Red Hat Enterprise Linux 7 RedHat php-0:5.4.16-36.ael7b_1 *
Red Hat Software Collections for Red Hat Enterprise Linux 6 RedHat php55-0:2.0-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6 RedHat php55-php-0:5.5.21-2.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6 RedHat php54-0:2.0-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6 RedHat php54-php-0:5.4.40-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6 RedHat php54-php-pecl-zendopcache-0:7.0.4-3.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.5 EUS RedHat php55-0:2.0-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.5 EUS RedHat php55-php-0:5.5.21-2.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.5 EUS RedHat php54-0:2.0-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.5 EUS RedHat php54-php-0:5.4.40-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.5 EUS RedHat php54-php-pecl-zendopcache-0:7.0.4-3.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.6 EUS RedHat php55-0:2.0-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.6 EUS RedHat php55-php-0:5.5.21-2.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.6 EUS RedHat php54-0:2.0-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.6 EUS RedHat php54-php-0:5.4.40-1.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 6.6 EUS RedHat php54-php-pecl-zendopcache-0:7.0.4-3.el6 *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat php55-0:2.0-1.el7 *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat php55-php-0:5.5.21-2.el7 *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat php54-0:2.0-1.el7 *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat php54-php-0:5.4.40-1.el7 *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat php54-php-pecl-zendopcache-0:7.0.4-3.el7 *
Php5 Ubuntu devel *
Php5 Ubuntu lucid *
Php5 Ubuntu precise *
Php5 Ubuntu trusty *
Php5 Ubuntu trusty/esm *
Php5 Ubuntu upstream *
Php5 Ubuntu utopic *

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