CVE Vulnerabilities

CVE-2015-1726

Use After Free

Published: Jun 10, 2015 | Modified: May 15, 2019
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
7.2 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
Ubuntu

Use-after-free vulnerability in the kernel-mode drivers in Microsoft Windows Server 2003 SP2 and R2 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allows local users to gain privileges via a crafted application, aka Microsoft Windows Kernel Brush Object Use After Free Vulnerability.

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
Windows_7 Microsoft - -
Windows_8 Microsoft - -
Windows_8.1 Microsoft - -
Windows_rt Microsoft - -
Windows_rt_8.1 Microsoft - -
Windows_server_2003 Microsoft - -
Windows_server_2003 Microsoft r2 r2
Windows_server_2008 Microsoft - -
Windows_server_2008 Microsoft r2 r2
Windows_server_2008 Microsoft r2 r2
Windows_server_2012 Microsoft - -
Windows_server_2012 Microsoft r2 r2
Windows_vista Microsoft - -

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 chances 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