ID CVE-2012-2895
Summary The PDF functionality in Google Chrome before 22.0.1229.79 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger out-of-bounds write operations.
Vulnerable Configurations
  • Google Chrome 22.0.1229.78
  • Google Chrome 22.0.1229.63
  • Google Chrome 22.0.1229.64
  • Google Chrome 22.0.1229.65
  • Google Chrome 22.0.1229.67
  • Google Chrome 22.0.1229.58
  • Google Chrome 22.0.1229.59
  • Google Chrome 22.0.1229.60
  • Google Chrome 22.0.1229.62
  • Google Chrome 22.0.1229.76
  • Google Chrome 22.0.1229.21
  • Google Chrome 22.0.1229.22
  • Google Chrome 22.0.1229.18
  • Google Chrome 22.0.1229.20
  • Google Chrome 22.0.1229.16
  • Google Chrome 22.0.1229.17
  • Google Chrome 22.0.1229.12
  • Google Chrome 22.0.1229.14
  • Google Chrome 22.0.1229.29
  • Google Chrome 22.0.1229.31
  • Google Chrome 22.0.1229.27
  • Google Chrome 22.0.1229.28
  • Google Chrome 22.0.1229.25
  • Google Chrome 22.0.1229.26
  • Google Chrome 22.0.1229.23
  • Google Chrome 22.0.1229.24
  • Google Chrome 22.0.1229.49
  • Google Chrome 22.0.1229.48
  • Google Chrome 22.0.1229.39
  • Google Chrome 22.0.1229.37
  • Google Chrome 22.0.1229.36
  • Google Chrome 22.0.1229.35
  • Google Chrome 22.0.1229.33
  • Google Chrome 22.0.1229.32
  • Google Chrome 22.0.1229.57
  • Google Chrome 22.0.1229.56
  • Google Chrome 22.0.1229.55
  • Google Chrome 22.0.1229.54
  • Google Chrome 22.0.1229.53
  • Google Chrome 22.0.1229.52
  • Google Chrome 22.0.1229.51
  • Google Chrome 22.0.1229.50
  • Google Chrome 22.0.1229.9
  • Google Chrome 22.0.1229.7
  • Google Chrome 22.0.1229.8
  • Google Chrome 22.0.1229.4
  • Google Chrome 22.0.1229.6
  • Google Chrome 22.0.1229.2
  • Google Chrome 22.0.1229.3
  • Google Chrome 22.0.1229.0
  • Google Chrome 22.0.1229.1
  • Google Chrome 22.0.1229.11
  • Google Chrome 22.0.1229.10
Base: 6.8 (as of 26-09-2012 - 15:25)
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
nessus via4
  • NASL family Windows
    NASL id GOOGLE_CHROME_22_0_1229_79.NASL
    description The version of Google Chrome installed on the remote host is earlier than 22.0.1229.79 and is, therefore, affected by the following vulnerabilities : - Out-of-bounds write errors exist related to Skia and the PDF viewer. (CVE-2012-2874, CVE-2012-2883, CVE-2012-2895) - Various, unspecified errors exist related to the PDF viewer. (CVE-2012-2875) - A buffer overflow error exists related to 'SSE2' optimizations. (CVE-2012-2876) - An unspecified error exists related to extensions and modal dialogs that can allow application crashes. (CVE-2012-2877) - Use-after-free errors exist related to plugin handling, 'onclick' handling, 'SVG' text references and the PDF viewer. (CVE-2012-2878, CVE-2012-2887, CVE-2012-2888, CVE-2012-2890) - An error exists related to 'DOM' topology corruption. (CVE-2012-2879) - Race conditions exist in the plugin paint buffer. (CVE-2012-2880) - 'DOM' tree corruption can occur with plugins. (CVE-2012-2881) - A pointer error exists related to 'OGG' container handling. (CVE-2012-2882) - An out-of-bounds read error exists related to Skia. (CVE-2012-2884) - The possibility of a double-free error exists related to application exit. (CVE-2012-2885) - Universal cross-site scripting issues exist related to the v8 JavaScript engine bindings and frame handling. (CVE-2012-2886, CVE-2012-2889) - Address information can be leaked via inter process communication (IPC). (CVE-2012-2891) - A bypass error exists related to pop-up block. (CVE-2012-2892) - A double-free error exists related to 'XSL' transforms. (CVE-2012-2893) - An error exists related to graphics context handling. (CVE-2012-2894) - An unspecified memory corruption issue exists in the Windows 7 kernel, as used by Google Chrome. (CVE-2012-2897) Successful exploitation of any of these issues could lead to an application crash or even allow arbitrary code execution, subject to the user's privileges.
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 62313
    published 2012-09-26
    reporter Tenable
    title Google Chrome < 22.0.1229.79 Multiple Vulnerabilities
  • NASL family FreeBSD Local Security Checks
    description Google Chrome Releases reports : [143439] High CVE-2012-2889: UXSS in frame handling. Credit to Sergey Glazunov. [143437] High CVE-2012-2886: UXSS in v8 bindings. Credit to Sergey Glazunov. [139814] High CVE-2012-2881: DOM tree corruption with plug-ins. Credit to Chamal de Silva. [135432] High CVE-2012-2876: Buffer overflow in SSE2 optimizations. Credit to Atte Kettunen of OUSPG. [140803] High CVE-2012-2883: Out-of-bounds write in Skia. Credit to Atte Kettunen of OUSPG. [143609] High CVE-2012-2887: Use-after-free in onclick handling. Credit to Atte Kettunen of OUSPG. [143656] High CVE-2012-2888: Use-after-free in SVG text references. Credit to miaubiz. [144899] High CVE-2012-2894: Crash in graphics context handling. Credit to Slawomir Blazek. [137707] Medium CVE-2012-2877: Browser crash with extensions and modal dialogs. Credit to Nir Moshe. [139168] Low CVE-2012-2879: DOM topology corruption. Credit to pawlkt. [141651] Medium CVE-2012-2884: Out-of-bounds read in Skia. Credit to Atte Kettunen of OUSPG. [132398] High CVE-2012-2874: Out-of-bounds write in Skia. Credit to Google Chrome Security Team (Inferno). [134955] [135488] [137106] [137288] [137302] [137547] [137556] [137606] [137635] [137880] [137928] [144579] [145079] [145121] [145163] [146462] Medium CVE-2012-2875: Various lower severity issues in the PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team. [137852] High CVE-2012-2878: Use-after-free in plug-in handling. Credit to Fermin Serna of Google Security Team. [139462] Medium CVE-2012-2880: Race condition in plug-in paint buffer. Credit to Google Chrome Security Team (Cris Neckar). [140647] High CVE-2012-2882: Wild pointer in OGG container handling. Credit to Google Chrome Security Team (Inferno). [142310] Medium CVE-2012-2885: Possible double free on exit. Credit to the Chromium development community. [143798] [144072] [147402] High CVE-2012-2890: Use-after-free in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team. [144051] Low CVE-2012-2891: Address leak over IPC. Credit to Lei Zhang of the Chromium development community. [144704] Low CVE-2012-2892: Pop-up block bypass. Credit to Google Chrome Security Team (Cris Neckar). [144799] High CVE-2012-2893: Double free in XSL transforms. Credit to Google Chrome Security Team (Cris Neckar). [145029] [145157] [146460] High CVE-2012-2895: Out-of-bounds writes in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
    last seen 2019-02-21
    modified 2013-06-21
    plugin id 62340
    published 2012-09-27
    reporter Tenable
    title FreeBSD : chromium -- multiple vulnerabilities (5bae2ab4-0820-11e2-be5f-00262d5ed8ee)
oval via4
accepted 2013-08-12T04:07:59.966-04:00
class vulnerability
  • name Shane Shaffer
    organization G2, Inc.
  • name Shane Shaffer
    organization G2, Inc.
  • name Maria Kedovskaya
    organization ALTX-SOFT
comment Google Chrome is installed
oval oval:org.mitre.oval:def:11914
description The PDF functionality in Google Chrome before 22.0.1229.79 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger out-of-bounds write operations.
family windows
id oval:org.mitre.oval:def:15773
status accepted
submitted 2012-09-26T08:38:26.230-04:00
title The PDF functionality in Google Chrome before 22.0.1229.79 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger out-of-bounds write operations
version 43
refmap via4
Last major update 02-11-2013 - 23:24
Published 26-09-2012 - 06:56
Last modified 18-09-2017 - 21:35
Back to Top