CVE Vulnerabilities

CVE-2016-5219

Use After Free

Published: Jan 19, 2017 | Modified: Nov 07, 2023
CVSS 3.x
6.3
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
4.3 MODERATE
AV:N/AC:M/Au:N/C:P/I:N/A:N
RedHat/V3
6.5 MODERATE
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM

A heap use after free in V8 in Google Chrome prior to 55.0.2883.75 for Mac, Windows and Linux, and 55.0.2883.84 for Android allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

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
Chrome Google * 54.0.2840.99 (including)
Red Hat Enterprise Linux 6 Supplementary RedHat chromium-browser-0:55.0.2883.75-1.el6 *
Chromium-browser Ubuntu artful *
Chromium-browser Ubuntu bionic *
Chromium-browser Ubuntu cosmic *
Chromium-browser Ubuntu devel *
Chromium-browser Ubuntu precise *
Chromium-browser Ubuntu trusty *
Chromium-browser Ubuntu upstream *
Chromium-browser Ubuntu xenial *
Chromium-browser Ubuntu yakkety *
Chromium-browser Ubuntu zesty *
Libv8 Ubuntu precise *
Libv8-3.14 Ubuntu artful *
Libv8-3.14 Ubuntu bionic *
Libv8-3.14 Ubuntu cosmic *
Libv8-3.14 Ubuntu devel *
Libv8-3.14 Ubuntu esm-apps/bionic *
Libv8-3.14 Ubuntu esm-apps/xenial *
Libv8-3.14 Ubuntu trusty *
Libv8-3.14 Ubuntu upstream *
Libv8-3.14 Ubuntu xenial *
Libv8-3.14 Ubuntu yakkety *
Libv8-3.14 Ubuntu zesty *
Oxide-qt Ubuntu artful *
Oxide-qt Ubuntu trusty *
Oxide-qt Ubuntu upstream *
Oxide-qt Ubuntu vivid/stable-phone-overlay *
Oxide-qt Ubuntu xenial *
Oxide-qt Ubuntu yakkety *
Oxide-qt Ubuntu zesty *

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