CVE Vulnerabilities

CVE-2012-0761

Improper Restriction of Operations within the Bounds of a Memory Buffer

Published: Feb 15, 2012 | Modified: Aug 29, 2017
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

The Shockwave 3D Asset component in Adobe Shockwave Player before 11.6.4.634 allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2012-0757, CVE-2012-0760, CVE-2012-0762, CVE-2012-0763, CVE-2012-0764, and CVE-2012-0766.

Weakness

The software 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
Shockwave_player Adobe 1.0 1.0
Shockwave_player Adobe 2.0 2.0
Shockwave_player Adobe 3.0 3.0
Shockwave_player Adobe 4.0 4.0
Shockwave_player Adobe 5.0 5.0
Shockwave_player Adobe 6.0 6.0
Shockwave_player Adobe 8.0 8.0
Shockwave_player Adobe 8.0.196 8.0.196
Shockwave_player Adobe 8.0.196a 8.0.196a
Shockwave_player Adobe 8.0.204 8.0.204
Shockwave_player Adobe 8.0.205 8.0.205
Shockwave_player Adobe 8.5.1 8.5.1
Shockwave_player Adobe 8.5.1.100 8.5.1.100
Shockwave_player Adobe 8.5.1.103 8.5.1.103
Shockwave_player Adobe 8.5.1.105 8.5.1.105
Shockwave_player Adobe 8.5.1.106 8.5.1.106
Shockwave_player Adobe 8.5.321 8.5.321
Shockwave_player Adobe 8.5.323 8.5.323
Shockwave_player Adobe 8.5.324 8.5.324
Shockwave_player Adobe 8.5.325 8.5.325
Shockwave_player Adobe 9 9
Shockwave_player Adobe 9.0.383 9.0.383
Shockwave_player Adobe 9.0.432 9.0.432
Shockwave_player Adobe 10.0.0.210 10.0.0.210
Shockwave_player Adobe 10.0.1.004 10.0.1.004
Shockwave_player Adobe 10.1.0.011 10.1.0.011
Shockwave_player Adobe 10.1.0.11 10.1.0.11
Shockwave_player Adobe 10.1.1.016 10.1.1.016
Shockwave_player Adobe 10.1.4.020 10.1.4.020
Shockwave_player Adobe 10.2.0.021 10.2.0.021
Shockwave_player Adobe 10.2.0.022 10.2.0.022
Shockwave_player Adobe 10.2.0.023 10.2.0.023
Shockwave_player Adobe 11.0.0.456 11.0.0.456
Shockwave_player Adobe 11.0.3.471 11.0.3.471
Shockwave_player Adobe 11.5.0.595 11.5.0.595
Shockwave_player Adobe 11.5.0.596 11.5.0.596
Shockwave_player Adobe 11.5.1.601 11.5.1.601
Shockwave_player Adobe 11.5.2.602 11.5.2.602
Shockwave_player Adobe 11.5.6.606 11.5.6.606
Shockwave_player Adobe 11.5.7.609 11.5.7.609
Shockwave_player Adobe 11.5.8.612 11.5.8.612
Shockwave_player Adobe 11.5.9.615 11.5.9.615
Shockwave_player Adobe 11.5.9.620 11.5.9.620
Shockwave_player Adobe 11.6.0.626 11.6.0.626
Shockwave_player Adobe 11.6.1.629 11.6.1.629
Shockwave_player Adobe * 11.6.3.633

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.

  • Run or compile the software using features or extensions that automatically provide a protection mechanism that mitigates or eliminates buffer overflows.

  • For example, certain compilers and extensions provide automatic buffer overflow detection mechanisms that are built into the compiled code. Examples include the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice.

  • 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].

References