ID CVE-2012-2891
Summary The IPC implementation in Google Chrome before 22.0.1229.79 allows attackers to obtain potentially sensitive information about memory addresses via unspecified vectors.
References
Vulnerable Configurations
  • Google Chrome 22.0.1229.78
    cpe:2.3:a:google:chrome:22.0.1229.78
  • Google Chrome 22.0.1229.63
    cpe:2.3:a:google:chrome:22.0.1229.63
  • Google Chrome 22.0.1229.64
    cpe:2.3:a:google:chrome:22.0.1229.64
  • Google Chrome 22.0.1229.65
    cpe:2.3:a:google:chrome:22.0.1229.65
  • Google Chrome 22.0.1229.67
    cpe:2.3:a:google:chrome:22.0.1229.67
  • Google Chrome 22.0.1229.58
    cpe:2.3:a:google:chrome:22.0.1229.58
  • Google Chrome 22.0.1229.59
    cpe:2.3:a:google:chrome:22.0.1229.59
  • Google Chrome 22.0.1229.60
    cpe:2.3:a:google:chrome:22.0.1229.60
  • Google Chrome 22.0.1229.62
    cpe:2.3:a:google:chrome:22.0.1229.62
  • Google Chrome 22.0.1229.76
    cpe:2.3:a:google:chrome:22.0.1229.76
  • Google Chrome 22.0.1229.21
    cpe:2.3:a:google:chrome:22.0.1229.21
  • Google Chrome 22.0.1229.22
    cpe:2.3:a:google:chrome:22.0.1229.22
  • Google Chrome 22.0.1229.18
    cpe:2.3:a:google:chrome:22.0.1229.18
  • Google Chrome 22.0.1229.20
    cpe:2.3:a:google:chrome:22.0.1229.20
  • Google Chrome 22.0.1229.16
    cpe:2.3:a:google:chrome:22.0.1229.16
  • Google Chrome 22.0.1229.17
    cpe:2.3:a:google:chrome:22.0.1229.17
  • Google Chrome 22.0.1229.12
    cpe:2.3:a:google:chrome:22.0.1229.12
  • Google Chrome 22.0.1229.14
    cpe:2.3:a:google:chrome:22.0.1229.14
  • Google Chrome 22.0.1229.29
    cpe:2.3:a:google:chrome:22.0.1229.29
  • Google Chrome 22.0.1229.31
    cpe:2.3:a:google:chrome:22.0.1229.31
  • Google Chrome 22.0.1229.27
    cpe:2.3:a:google:chrome:22.0.1229.27
  • Google Chrome 22.0.1229.28
    cpe:2.3:a:google:chrome:22.0.1229.28
  • Google Chrome 22.0.1229.25
    cpe:2.3:a:google:chrome:22.0.1229.25
  • Google Chrome 22.0.1229.26
    cpe:2.3:a:google:chrome:22.0.1229.26
  • Google Chrome 22.0.1229.23
    cpe:2.3:a:google:chrome:22.0.1229.23
  • Google Chrome 22.0.1229.24
    cpe:2.3:a:google:chrome:22.0.1229.24
  • Google Chrome 22.0.1229.49
    cpe:2.3:a:google:chrome:22.0.1229.49
  • Google Chrome 22.0.1229.48
    cpe:2.3:a:google:chrome:22.0.1229.48
  • Google Chrome 22.0.1229.39
    cpe:2.3:a:google:chrome:22.0.1229.39
  • Google Chrome 22.0.1229.37
    cpe:2.3:a:google:chrome:22.0.1229.37
  • Google Chrome 22.0.1229.36
    cpe:2.3:a:google:chrome:22.0.1229.36
  • Google Chrome 22.0.1229.35
    cpe:2.3:a:google:chrome:22.0.1229.35
  • Google Chrome 22.0.1229.33
    cpe:2.3:a:google:chrome:22.0.1229.33
  • Google Chrome 22.0.1229.32
    cpe:2.3:a:google:chrome:22.0.1229.32
  • Google Chrome 22.0.1229.57
    cpe:2.3:a:google:chrome:22.0.1229.57
  • Google Chrome 22.0.1229.56
    cpe:2.3:a:google:chrome:22.0.1229.56
  • Google Chrome 22.0.1229.55
    cpe:2.3:a:google:chrome:22.0.1229.55
  • Google Chrome 22.0.1229.54
    cpe:2.3:a:google:chrome:22.0.1229.54
  • Google Chrome 22.0.1229.53
    cpe:2.3:a:google:chrome:22.0.1229.53
  • Google Chrome 22.0.1229.52
    cpe:2.3:a:google:chrome:22.0.1229.52
  • Google Chrome 22.0.1229.51
    cpe:2.3:a:google:chrome:22.0.1229.51
  • Google Chrome 22.0.1229.50
    cpe:2.3:a:google:chrome:22.0.1229.50
  • Google Chrome 22.0.1229.9
    cpe:2.3:a:google:chrome:22.0.1229.9
  • Google Chrome 22.0.1229.7
    cpe:2.3:a:google:chrome:22.0.1229.7
  • Google Chrome 22.0.1229.8
    cpe:2.3:a:google:chrome:22.0.1229.8
  • Google Chrome 22.0.1229.4
    cpe:2.3:a:google:chrome:22.0.1229.4
  • Google Chrome 22.0.1229.6
    cpe:2.3:a:google:chrome:22.0.1229.6
  • Google Chrome 22.0.1229.2
    cpe:2.3:a:google:chrome:22.0.1229.2
  • Google Chrome 22.0.1229.3
    cpe:2.3:a:google:chrome:22.0.1229.3
  • Google Chrome 22.0.1229.0
    cpe:2.3:a:google:chrome:22.0.1229.0
  • Google Chrome 22.0.1229.1
    cpe:2.3:a:google:chrome:22.0.1229.1
  • Google Chrome 22.0.1229.11
    cpe:2.3:a:google:chrome:22.0.1229.11
  • Google Chrome 22.0.1229.10
    cpe:2.3:a:google:chrome:22.0.1229.10
CVSS
Base: 5.0 (as of 26-09-2012 - 15:21)
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
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
    source https://www.tenable.com/plugins/index.php?view=single&id=62313
    title Google Chrome < 22.0.1229.79 Multiple Vulnerabilities
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2012-721.NASL
    description Chromium was upgraded to version 24.0.1290 which fixed multiple security flaws.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 74788
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74788
    title openSUSE Security Update : chromium (openSUSE-SU-2012:1376-1)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201210-07.NASL
    description The remote host is affected by the vulnerability described in GLSA-201210-07 (Chromium: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Chromium. Please review the CVE identifiers and release notes referenced below for details. Impact : A remote attacker could entice a user to open a specially crafted web site using Chromium, possibly resulting in the execution of arbitrary code with the privileges of the process, arbitrary file write, a Denial of Service condition, Cross-Site Scripting in SSL interstitial and various Universal Cross-Site Scripting attacks. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-11
    plugin id 62652
    published 2012-10-22
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=62652
    title GLSA-201210-07 : Chromium: Multiple vulnerabilities
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_5BAE2AB4082011E2BE5F00262D5ED8EE.NASL
    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
    source https://www.tenable.com/plugins/index.php?view=single&id=62340
    title FreeBSD : chromium -- multiple vulnerabilities (5bae2ab4-0820-11e2-be5f-00262d5ed8ee)
oval via4
accepted 2013-08-12T04:07:35.903-04:00
class vulnerability
contributors
  • name Shane Shaffer
    organization G2, Inc.
  • name Shane Shaffer
    organization G2, Inc.
  • name Maria Kedovskaya
    organization ALTX-SOFT
definition_extensions
comment Google Chrome is installed
oval oval:org.mitre.oval:def:11914
description The IPC implementation in Google Chrome before 22.0.1229.79 allows attackers to obtain potentially sensitive information about memory addresses via unspecified vectors.
family windows
id oval:org.mitre.oval:def:15484
status accepted
submitted 2012-09-26T08:38:26.230-04:00
title The IPC implementation in Google Chrome before 22.0.1229.79 allows attackers to obtain potentially sensitive information about memory addresses via unspecified vectors
version 43
refmap via4
confirm
suse openSUSE-SU-2012:1376
xf google-chrome-cve20122891(78842)
Last major update 02-11-2013 - 23:24
Published 26-09-2012 - 06:56
Last modified 18-09-2017 - 21:35
Back to Top