Google Chrome before 21.0.1180.57 on Linux does not properly handle tabs, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via unspecified vectors.
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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Chrome | * | 21.0.1180.56 (including) | |
| Chrome | 21.0.1180.0 (including) | 21.0.1180.0 (including) | |
| Chrome | 21.0.1180.1 (including) | 21.0.1180.1 (including) | |
| Chrome | 21.0.1180.2 (including) | 21.0.1180.2 (including) | |
| Chrome | 21.0.1180.31 (including) | 21.0.1180.31 (including) | |
| Chrome | 21.0.1180.32 (including) | 21.0.1180.32 (including) | |
| Chrome | 21.0.1180.33 (including) | 21.0.1180.33 (including) | |
| Chrome | 21.0.1180.34 (including) | 21.0.1180.34 (including) | |
| Chrome | 21.0.1180.35 (including) | 21.0.1180.35 (including) | |
| Chrome | 21.0.1180.36 (including) | 21.0.1180.36 (including) | |
| Chrome | 21.0.1180.37 (including) | 21.0.1180.37 (including) | |
| Chrome | 21.0.1180.38 (including) | 21.0.1180.38 (including) | |
| Chrome | 21.0.1180.39 (including) | 21.0.1180.39 (including) | |
| Chrome | 21.0.1180.41 (including) | 21.0.1180.41 (including) | |
| Chrome | 21.0.1180.46 (including) | 21.0.1180.46 (including) | |
| Chrome | 21.0.1180.47 (including) | 21.0.1180.47 (including) | |
| Chrome | 21.0.1180.48 (including) | 21.0.1180.48 (including) | |
| Chrome | 21.0.1180.49 (including) | 21.0.1180.49 (including) | |
| Chrome | 21.0.1180.50 (including) | 21.0.1180.50 (including) | |
| Chrome | 21.0.1180.51 (including) | 21.0.1180.51 (including) | |
| Chrome | 21.0.1180.52 (including) | 21.0.1180.52 (including) | |
| Chrome | 21.0.1180.53 (including) | 21.0.1180.53 (including) | |
| Chrome | 21.0.1180.54 (including) | 21.0.1180.54 (including) | |
| Chrome | 21.0.1180.55 (including) | 21.0.1180.55 (including) | |
| Chromium-browser | Ubuntu | lucid | * |
| Chromium-browser | Ubuntu | natty | * |
| Chromium-browser | Ubuntu | oneiric | * |
| Chromium-browser | Ubuntu | precise | * |
| Chromium-browser | Ubuntu | quantal | * |
| Chromium-browser | Ubuntu | upstream | * |
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.
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].