ID CVE-2012-5123
Summary Skia, as used in Google Chrome before 23.0.1271.64, allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified vectors.
References
Vulnerable Configurations
  • Google Chrome 23.0.1271.62
    cpe:2.3:a:google:chrome:23.0.1271.62
  • Google Chrome 23.0.1271.0
    cpe:2.3:a:google:chrome:23.0.1271.0
  • Google Chrome 23.0.1271.8
    cpe:2.3:a:google:chrome:23.0.1271.8
  • Google Chrome 23.0.1271.7
    cpe:2.3:a:google:chrome:23.0.1271.7
  • Google Chrome 23.0.1271.6
    cpe:2.3:a:google:chrome:23.0.1271.6
  • Google Chrome 23.0.1271.5
    cpe:2.3:a:google:chrome:23.0.1271.5
  • Google Chrome 23.0.1271.4
    cpe:2.3:a:google:chrome:23.0.1271.4
  • Google Chrome 23.0.1271.3
    cpe:2.3:a:google:chrome:23.0.1271.3
  • Google Chrome 23.0.1271.2
    cpe:2.3:a:google:chrome:23.0.1271.2
  • Google Chrome 23.0.1271.1
    cpe:2.3:a:google:chrome:23.0.1271.1
  • Google Chrome 23.0.1271.15
    cpe:2.3:a:google:chrome:23.0.1271.15
  • Google Chrome 23.0.1271.16
    cpe:2.3:a:google:chrome:23.0.1271.16
  • Google Chrome 23.0.1271.13
    cpe:2.3:a:google:chrome:23.0.1271.13
  • Google Chrome 23.0.1271.14
    cpe:2.3:a:google:chrome:23.0.1271.14
  • Google Chrome 23.0.1271.11
    cpe:2.3:a:google:chrome:23.0.1271.11
  • Google Chrome 23.0.1271.12
    cpe:2.3:a:google:chrome:23.0.1271.12
  • Google Chrome 23.0.1271.9
    cpe:2.3:a:google:chrome:23.0.1271.9
  • Google Chrome 23.0.1271.10
    cpe:2.3:a:google:chrome:23.0.1271.10
  • Google Chrome 23.0.1271.23
    cpe:2.3:a:google:chrome:23.0.1271.23
  • Google Chrome 23.0.1271.24
    cpe:2.3:a:google:chrome:23.0.1271.24
  • Google Chrome 23.0.1271.21
    cpe:2.3:a:google:chrome:23.0.1271.21
  • Google Chrome 23.0.1271.22
    cpe:2.3:a:google:chrome:23.0.1271.22
  • Google Chrome 23.0.1271.19
    cpe:2.3:a:google:chrome:23.0.1271.19
  • Google Chrome 23.0.1271.20
    cpe:2.3:a:google:chrome:23.0.1271.20
  • Google Chrome 23.0.1271.17
    cpe:2.3:a:google:chrome:23.0.1271.17
  • Google Chrome 23.0.1271.18
    cpe:2.3:a:google:chrome:23.0.1271.18
  • Google Chrome 23.0.1271.61
    cpe:2.3:a:google:chrome:23.0.1271.61
  • Google Chrome 23.0.1271.60
    cpe:2.3:a:google:chrome:23.0.1271.60
  • Google Chrome 23.0.1271.59
    cpe:2.3:a:google:chrome:23.0.1271.59
  • Google Chrome 23.0.1271.58
    cpe:2.3:a:google:chrome:23.0.1271.58
  • Google Chrome 23.0.1271.53
    cpe:2.3:a:google:chrome:23.0.1271.53
  • Google Chrome 23.0.1271.52
    cpe:2.3:a:google:chrome:23.0.1271.52
  • Google Chrome 23.0.1271.51
    cpe:2.3:a:google:chrome:23.0.1271.51
  • Google Chrome 23.0.1271.50
    cpe:2.3:a:google:chrome:23.0.1271.50
  • Google Chrome 23.0.1271.57
    cpe:2.3:a:google:chrome:23.0.1271.57
  • Google Chrome 23.0.1271.56
    cpe:2.3:a:google:chrome:23.0.1271.56
  • Google Chrome 23.0.1271.55
    cpe:2.3:a:google:chrome:23.0.1271.55
  • Google Chrome 23.0.1271.54
    cpe:2.3:a:google:chrome:23.0.1271.54
  • Google Chrome 23.0.1271.40
    cpe:2.3:a:google:chrome:23.0.1271.40
  • Google Chrome 23.0.1271.41
    cpe:2.3:a:google:chrome:23.0.1271.41
  • Google Chrome 23.0.1271.38
    cpe:2.3:a:google:chrome:23.0.1271.38
  • Google Chrome 23.0.1271.39
    cpe:2.3:a:google:chrome:23.0.1271.39
  • Google Chrome 23.0.1271.46
    cpe:2.3:a:google:chrome:23.0.1271.46
  • Google Chrome 23.0.1271.49
    cpe:2.3:a:google:chrome:23.0.1271.49
  • Google Chrome 23.0.1271.44
    cpe:2.3:a:google:chrome:23.0.1271.44
  • Google Chrome 23.0.1271.45
    cpe:2.3:a:google:chrome:23.0.1271.45
  • Google Chrome 23.0.1271.31
    cpe:2.3:a:google:chrome:23.0.1271.31
  • Google Chrome 23.0.1271.32
    cpe:2.3:a:google:chrome:23.0.1271.32
  • Google Chrome 23.0.1271.26
    cpe:2.3:a:google:chrome:23.0.1271.26
  • Google Chrome 23.0.1271.30
    cpe:2.3:a:google:chrome:23.0.1271.30
  • Google Chrome 23.0.1271.36
    cpe:2.3:a:google:chrome:23.0.1271.36
  • Google Chrome 23.0.1271.37
    cpe:2.3:a:google:chrome:23.0.1271.37
  • Google Chrome 23.0.1271.33
    cpe:2.3:a:google:chrome:23.0.1271.33
  • Google Chrome 23.0.1271.35
    cpe:2.3:a:google:chrome:23.0.1271.35
CVSS
Base: 5.0 (as of 28-09-2016 - 09:51)
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • 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.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE NONE PARTIAL
nessus via4
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_209C068D28BE11E2916000262D5ED8EE.NASL
    description Google Chrome Releases reports : [157079] Medium CVE-2012-5127: Integer overflow leading to out-of-bounds read in WebP handling. Credit to Phil Turnbull. [Linux 64-bit only] [150729] Medium CVE-2012-5120: Out-of-bounds array access in v8. Credit to Atte Kettunen of OUSPG. [143761] High CVE-2012-5116: Use-after-free in SVG filter handling. Credit to miaubiz. [Mac OS only] [149717] High CVE-2012-5118: Integer bounds check issue in GPU command buffers. Credit to miaubiz. [154055] High CVE-2012-5121: Use-after-free in video layout. Credit to Atte Kettunen of OUSPG. [145915] Low CVE-2012-5117: Inappropriate load of SVG subresource in img context. Credit to Felix Grobert of the Google Security Team. [149759] Medium CVE-2012-5119: Race condition in Pepper buffer handling. Credit to Fermin Serna of the Google Security Team. [154465] Medium CVE-2012-5122: Bad cast in input handling. Credit to Google Chrome Security Team (Inferno). [154590] [156826] Medium CVE-2012-5123: Out-of-bounds reads in Skia. Credit to Google Chrome Security Team (Inferno). [155323] High CVE-2012-5124: Memory corruption in texture handling. Credit to Al Patrick of the Chromium development community. [156051] Medium CVE-2012-5125: Use-after-free in extension tab handling. Credit to Alexander Potapenko of the Chromium development community. [156366] Medium CVE-2012-5126: Use-after-free in plug-in placeholder handling. Credit to Google Chrome Security Team (Inferno). [157124] High CVE-2012-5128: Bad write in v8. Credit to Google Chrome Security Team (Cris Neckar).
    last seen 2019-02-21
    modified 2016-05-26
    plugin id 62856
    published 2012-11-08
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=62856
    title FreeBSD : chromium -- multiple vulnerabilities (209c068d-28be-11e2-9160-00262d5ed8ee)
  • NASL family Windows
    NASL id GOOGLE_CHROME_23_0_1271_64.NASL
    description The version of Google Chrome installed on the remote host is earlier than 23.0.1271.64 and is, therefore, affected by the following vulnerabilities : - Use-after-free errors exist related to SVG filter handling, video layout, extension tab handling and plug-in placeholder handling. (CVE-2012-5116, CVE-2012-5121, CVE-2012-5125, CVE-2012-5126) - An error exists related to inappropriate SVG subresource loading in the 'img' context. (CVE-2012-5117) - A race condition exists related to 'Pepper' buffer handling. (CVE-2012-5119) - A bad cast error exists related to input handling. (CVE-2012-5122) - Out-of-bounds reads exist related to Skia. (CVE-2012-5123) - A memory corruption error exists related to texture handling. (CVE-2012-5124) - An integer overflow error exists related to 'WebP' handling. This error can lead to out-of-bounds reads. (CVE-2012-5127) - An improper write error exists related to the 'v8' JavaScript engine. (CVE-2012-5128) 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 62861
    published 2012-11-08
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=62861
    title Google Chrome < 23.0.1271.64 Multiple Vulnerabilities
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201309-16.NASL
    description The remote host is affected by the vulnerability described in GLSA-201309-16 (Chromium, V8: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Chromium and V8. Please review the CVE identifiers and release notes referenced below for details. Impact : A context-dependent attacker could entice a user to open a specially crafted website or JavaScript program using Chromium or V8, possibly resulting in the execution of arbitrary code with the privileges of the process or a Denial of Service condition. Furthermore, a remote attacker may be able to bypass security restrictions or have other, unspecified, impact. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 70112
    published 2013-09-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=70112
    title GLSA-201309-16 : Chromium, V8: Multiple vulnerabilities
oval via4
accepted 2013-08-12T04:07:49.367-04:00
class vulnerability
contributors
  • 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 Skia, as used in Google Chrome before 23.0.1271.64, allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified vectors.
family windows
id oval:org.mitre.oval:def:15631
status accepted
submitted 2012-11-07T10:16:29.050-05:00
title Skia, as used in Google Chrome before 23.0.1271.64, allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified vectors
version 42
refmap via4
bid 56413
confirm
osvdb 87077
xf chrome-cve20125123-code-exec(79870)
Last major update 28-09-2016 - 10:00
Published 07-11-2012 - 06:43
Last modified 18-09-2017 - 21:35
Back to Top