CVE Vulnerabilities

CVE-2013-2856

Use After Free

Published: Jun 05, 2013 | Modified: Sep 19, 2017
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
RedHat/V3
Ubuntu

Use-after-free vulnerability in Google Chrome before 27.0.1453.110 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the handling of input.

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 27.0.1453.107 27.0.1453.107
Chrome Google * 27.0.1453.109
Chrome Google 27.0.1453.77 27.0.1453.77
Chrome Google 27.0.1453.105 27.0.1453.105
Chrome Google 27.0.1453.74 27.0.1453.74
Chrome Google 27.0.1453.61 27.0.1453.61
Chrome Google 27.0.1453.62 27.0.1453.62
Chrome Google 27.0.1453.34 27.0.1453.34
Chrome Google 27.0.1453.11 27.0.1453.11
Chrome Google 27.0.1453.47 27.0.1453.47
Chrome Google 27.0.1453.81 27.0.1453.81
Chrome Google 27.0.1453.102 27.0.1453.102
Chrome Google 27.0.1453.54 27.0.1453.54
Chrome Google 27.0.1453.41 27.0.1453.41
Chrome Google 27.0.1453.10 27.0.1453.10
Chrome Google 27.0.1453.42 27.0.1453.42
Chrome Google 27.0.1453.59 27.0.1453.59
Chrome Google 27.0.1453.7 27.0.1453.7
Chrome Google 27.0.1453.93 27.0.1453.93
Chrome Google 27.0.1453.70 27.0.1453.70
Chrome Google 27.0.1453.69 27.0.1453.69
Chrome Google 27.0.1453.51 27.0.1453.51
Chrome Google 27.0.1453.103 27.0.1453.103
Chrome Google 27.0.1453.6 27.0.1453.6
Chrome Google 27.0.1453.38 27.0.1453.38
Chrome Google 27.0.1453.65 27.0.1453.65
Chrome Google 27.0.1453.56 27.0.1453.56
Chrome Google 27.0.1453.71 27.0.1453.71
Chrome Google 27.0.1453.84 27.0.1453.84
Chrome Google 27.0.1453.57 27.0.1453.57
Chrome Google 27.0.1453.58 27.0.1453.58
Chrome Google 27.0.1453.91 27.0.1453.91
Chrome Google 27.0.1453.68 27.0.1453.68
Chrome Google 27.0.1453.73 27.0.1453.73
Chrome Google 27.0.1453.108 27.0.1453.108
Chrome Google 27.0.1453.106 27.0.1453.106
Chrome Google 27.0.1453.35 27.0.1453.35
Chrome Google 27.0.1453.86 27.0.1453.86
Chrome Google 27.0.1453.76 27.0.1453.76
Chrome Google 27.0.1453.36 27.0.1453.36
Chrome Google 27.0.1453.94 27.0.1453.94
Chrome Google 27.0.1453.4 27.0.1453.4
Chrome Google 27.0.1453.37 27.0.1453.37
Chrome Google 27.0.1453.89 27.0.1453.89
Chrome Google 27.0.1453.52 27.0.1453.52
Chrome Google 27.0.1453.88 27.0.1453.88
Chrome Google 27.0.1453.1 27.0.1453.1
Chrome Google 27.0.1453.90 27.0.1453.90
Chrome Google 27.0.1453.39 27.0.1453.39
Chrome Google 27.0.1453.13 27.0.1453.13
Chrome Google 27.0.1453.9 27.0.1453.9
Chrome Google 27.0.1453.44 27.0.1453.44
Chrome Google 27.0.1453.78 27.0.1453.78
Chrome Google 27.0.1453.40 27.0.1453.40
Chrome Google 27.0.1453.3 27.0.1453.3
Chrome Google 27.0.1453.85 27.0.1453.85
Chrome Google 27.0.1453.43 27.0.1453.43
Chrome Google 27.0.1453.49 27.0.1453.49
Chrome Google 27.0.1453.80 27.0.1453.80
Chrome Google 27.0.1453.87 27.0.1453.87
Chrome Google 27.0.1453.64 27.0.1453.64
Chrome Google 27.0.1453.0 27.0.1453.0
Chrome Google 27.0.1453.67 27.0.1453.67
Chrome Google 27.0.1453.45 27.0.1453.45
Chrome Google 27.0.1453.55 27.0.1453.55
Chrome Google 27.0.1453.82 27.0.1453.82
Chrome Google 27.0.1453.75 27.0.1453.75
Chrome Google 27.0.1453.46 27.0.1453.46
Chrome Google 27.0.1453.83 27.0.1453.83
Chrome Google 27.0.1453.72 27.0.1453.72
Chrome Google 27.0.1453.15 27.0.1453.15
Chrome Google 27.0.1453.60 27.0.1453.60
Chrome Google 27.0.1453.50 27.0.1453.50
Chrome Google 27.0.1453.63 27.0.1453.63
Chrome Google 27.0.1453.2 27.0.1453.2
Chrome Google 27.0.1453.8 27.0.1453.8
Chrome Google 27.0.1453.66 27.0.1453.66
Chrome Google 27.0.1453.104 27.0.1453.104
Chrome Google 27.0.1453.79 27.0.1453.79
Chrome Google 27.0.1453.5 27.0.1453.5
Chrome Google 27.0.1453.12 27.0.1453.12

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