CVE Vulnerabilities

CVE-2013-3345

Improper Restriction of Operations within the Bounds of a Memory Buffer

Published: Jul 10, 2013 | Modified: Aug 22, 2013
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
10 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
Ubuntu

Adobe Flash Player before 11.7.700.232 and 11.8.x before 11.8.800.94 on Windows and Mac OS X, before 11.2.202.297 on Linux, before 11.1.111.64 on Android 2.x and 3.x, and before 11.1.115.69 on Android 4.x allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.

Weakness

The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.

Affected Software

Name Vendor Start Version End Version
Flash_player Adobe * 11.7.700.224
Flash_player Adobe 11.0 11.0
Flash_player Adobe 11.0.1.152 11.0.1.152
Flash_player Adobe 11.0.1.153 11.0.1.153
Flash_player Adobe 11.1 11.1
Flash_player Adobe 11.1.102.55 11.1.102.55
Flash_player Adobe 11.1.102.59 11.1.102.59
Flash_player Adobe 11.1.102.62 11.1.102.62
Flash_player Adobe 11.1.102.63 11.1.102.63
Flash_player Adobe 11.1.111.8 11.1.111.8
Flash_player Adobe 11.1.111.44 11.1.111.44
Flash_player Adobe 11.1.111.50 11.1.111.50
Flash_player Adobe 11.1.111.54 11.1.111.54
Flash_player Adobe 11.1.115.7 11.1.115.7
Flash_player Adobe 11.1.115.34 11.1.115.34
Flash_player Adobe 11.1.115.48 11.1.115.48
Flash_player Adobe 11.1.115.54 11.1.115.54
Flash_player Adobe 11.1.115.58 11.1.115.58
Flash_player Adobe 11.2.202.223 11.2.202.223
Flash_player Adobe 11.2.202.228 11.2.202.228
Flash_player Adobe 11.2.202.233 11.2.202.233
Flash_player Adobe 11.2.202.235 11.2.202.235
Flash_player Adobe 11.2.202.236 11.2.202.236
Flash_player Adobe 11.2.202.238 11.2.202.238
Flash_player Adobe 11.2.202.243 11.2.202.243
Flash_player Adobe 11.2.202.251 11.2.202.251
Flash_player Adobe 11.2.202.258 11.2.202.258
Flash_player Adobe 11.2.202.261 11.2.202.261
Flash_player Adobe 11.2.202.262 11.2.202.262
Flash_player Adobe 11.2.202.270 11.2.202.270
Flash_player Adobe 11.2.202.273 11.2.202.273
Flash_player Adobe 11.2.202.275 11.2.202.275
Flash_player Adobe 11.2.202.280 11.2.202.280
Flash_player Adobe 11.2.202.285 11.2.202.285
Flash_player Adobe 11.3.300.257 11.3.300.257
Flash_player Adobe 11.3.300.262 11.3.300.262
Flash_player Adobe 11.3.300.265 11.3.300.265
Flash_player Adobe 11.3.300.268 11.3.300.268
Flash_player Adobe 11.3.300.270 11.3.300.270
Flash_player Adobe 11.3.300.271 11.3.300.271
Flash_player Adobe 11.3.300.273 11.3.300.273
Flash_player Adobe 11.4.402.265 11.4.402.265
Flash_player Adobe 11.4.402.278 11.4.402.278
Flash_player Adobe 11.4.402.287 11.4.402.287
Flash_player Adobe 11.5.502.110 11.5.502.110
Flash_player Adobe 11.5.502.135 11.5.502.135
Flash_player Adobe 11.5.502.136 11.5.502.136
Flash_player Adobe 11.5.502.146 11.5.502.146
Flash_player Adobe 11.5.502.149 11.5.502.149
Flash_player Adobe 11.6.602.167 11.6.602.167
Flash_player Adobe 11.6.602.168 11.6.602.168
Flash_player Adobe 11.6.602.171 11.6.602.171
Flash_player Adobe 11.6.602.180 11.6.602.180
Flash_player Adobe 11.7.700.169 11.7.700.169
Flash_player Adobe 11.7.700.202 11.7.700.202

Extended Description

Certain languages allow direct addressing of memory locations and do not automatically ensure that these locations are valid for the memory buffer that is being referenced. This can cause read or write operations to be performed on memory locations that may be associated with other variables, data structures, or internal program data. As a result, an attacker may be able to execute arbitrary code, alter the intended control flow, read sensitive information, or cause the system to crash.

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

  • For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer.

  • Be wary that a language’s interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

  • Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.

  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.

  • Consider adhering to the following rules when allocating and managing an application’s memory:

  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.

  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.

  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

  • Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment.

  • For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336].

References