ID CVE-2012-5117
Summary Google Chrome before 23.0.1271.64 does not properly restrict the loading of an SVG subresource in the context of an IMG element, which has unspecified impact and remote attack 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: 7.5 (as of 28-09-2016 - 10:20)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL 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:08:09.432-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 Google Chrome before 23.0.1271.64 does not properly restrict the loading of an SVG subresource in the context of an IMG element, which has unspecified impact and remote attack vectors.
family windows
id oval:org.mitre.oval:def:15912
status accepted
submitted 2012-11-07T10:16:29.050-05:00
title Google Chrome before 23.0.1271.64 does not properly restrict the loading of an SVG subresource in the context of an IMG element
version 42
refmap via4
bid 56413
confirm
osvdb 87076
Last major update 28-09-2016 - 10:49
Published 07-11-2012 - 06:43
Last modified 18-09-2017 - 21:35
Back to Top