ID CVE-2012-2897
Summary The kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7 Gold and SP1, Windows 8, Windows Server 2012, and Windows RT, as used by Google Chrome before 22.0.1229.79 and other programs, do not properly handle objects in memory, which allows remote attackers to execute arbitrary code via a crafted TrueType font file, aka "Windows Font Parsing Vulnerability" or "TrueType Font Parsing Vulnerability."
References
Vulnerable Configurations
  • 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.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.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.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.9
    cpe:2.3:a:google:chrome:22.0.1229.9
  • Google Chrome 22.0.1229.10
    cpe:2.3:a:google:chrome:22.0.1229.10
  • Google Chrome 22.0.1229.11
    cpe:2.3:a:google:chrome:22.0.1229.11
  • 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.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.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.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.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.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.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.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.32
    cpe:2.3:a:google:chrome:22.0.1229.32
  • Google Chrome 22.0.1229.33
    cpe:2.3:a:google:chrome:22.0.1229.33
  • Google Chrome 22.0.1229.35
    cpe:2.3:a:google:chrome:22.0.1229.35
  • Google Chrome 22.0.1229.36
    cpe:2.3:a:google:chrome:22.0.1229.36
  • Google Chrome 22.0.1229.37
    cpe:2.3:a:google:chrome:22.0.1229.37
  • Google Chrome 22.0.1229.39
    cpe:2.3:a:google:chrome:22.0.1229.39
  • Google Chrome 22.0.1229.48
    cpe:2.3:a:google:chrome:22.0.1229.48
  • Google Chrome 22.0.1229.49
    cpe:2.3:a:google:chrome:22.0.1229.49
  • Google Chrome 22.0.1229.50
    cpe:2.3:a:google:chrome:22.0.1229.50
  • Google Chrome 22.0.1229.51
    cpe:2.3:a:google:chrome:22.0.1229.51
  • Google Chrome 22.0.1229.52
    cpe:2.3:a:google:chrome:22.0.1229.52
  • Google Chrome 22.0.1229.53
    cpe:2.3:a:google:chrome:22.0.1229.53
  • Google Chrome 22.0.1229.54
    cpe:2.3:a:google:chrome:22.0.1229.54
  • Google Chrome 22.0.1229.55
    cpe:2.3:a:google:chrome:22.0.1229.55
  • Google Chrome 22.0.1229.56
    cpe:2.3:a:google:chrome:22.0.1229.56
  • Google Chrome 22.0.1229.57
    cpe:2.3:a:google:chrome:22.0.1229.57
  • 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.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.76
    cpe:2.3:a:google:chrome:22.0.1229.76
  • Google Chrome 22.0.1229.78
    cpe:2.3:a:google:chrome:22.0.1229.78
  • Microsoft Windows 7
    cpe:2.3:o:microsoft:windows_7
  • Microsoft Windows 7 64-bit Service Pack 1 (initial release)
    cpe:2.3:o:microsoft:windows_7:-:sp1:x64
  • Microsoft Windows 7 x86 Service Pack 1
    cpe:2.3:o:microsoft:windows_7:-:sp1:x86
  • Windows 8 x64 (64-bit)
    cpe:2.3:o:microsoft:windows_8:-:-:x64
  • Windows 8 x86 (32-bit)
    cpe:2.3:o:microsoft:windows_8:-:-:x86
  • Microsoft Windows RT
    cpe:2.3:o:microsoft:windows_rt
  • Microsoft Windows Server 2003 Service Pack 2
    cpe:2.3:o:microsoft:windows_server_2003:-:sp2
  • Windows Server 2008 R2 for Itanium-based Systems
    cpe:2.3:o:microsoft:windows_server_2008:-:r2:itanium
  • Windows Server 2008 R2 for x64-based Systems
    cpe:2.3:o:microsoft:windows_server_2008:-:r2:x64
  • Microsoft Windows Server 2008 Service Pack 2 x64 (64-bit)
    cpe:2.3:o:microsoft:windows_server_2008:-:sp2:x64
  • Windows Server 2008 Service Pack 2 x86
    cpe:2.3:o:microsoft:windows_server_2008:-:sp2:x86
  • Microsoft Windows Server 2008 Service Pack 2 for Itanium-Based Systems
    cpe:2.3:o:microsoft:windows_server_2008:-:sp2:itanium
  • Microsoft Windows Server 2008 r2 Service Pack 1 Itanium
    cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:itanium
  • Microsoft Windows Server 2008 R2 Service Pack 1 x64 (64-bit)
    cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:x64
  • Microsoft Windows Server 2012
    cpe:2.3:o:microsoft:windows_server_2012
  • Microsoft Windows Vista Service Pack 2 x64 (64-bit)
    cpe:2.3:o:microsoft:windows_vista:-:sp2:x64
  • Microsoft Windows Vista Service Pack 2
    cpe:2.3:o:microsoft:windows_vista:-:sp2
  • Microsoft Windows XP Service Pack 3
    cpe:2.3:o:microsoft:windows_xp:-:sp3
  • Microsoft Windows XP Service Pack 2 x64 (64-bit)
    cpe:2.3:o:microsoft:windows_xp:-:sp2:x64
CVSS
Base: 10.0 (as of 26-09-2012 - 15:30)
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
COMPLETE COMPLETE COMPLETE
msbulletin via4
bulletin_id MS12-075
bulletin_url
date 2012-11-13T00:00:00
impact Remote Code Execution
knowledgebase_id 2761226
knowledgebase_url
severity Critical
title Vulnerabilities in Windows Kernel-Mode Drivers Could Allow Remote Code Execution
nessus via4
  • NASL family Windows : Microsoft Bulletins
    NASL id SMB_NT_MS12-075.NASL
    description The remote Windows host is affected by the following remote code execution vulnerabilities: - Two use-after-free vulnerabilities exist within Windows kernel-mode drivers. (CVE-2012-2530, CVE-2012-2553) - A TrueType Font Parsing vulnerability exists due to the way TrueType font files are handled. (CVE-2012-2897)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 62907
    published 2012-11-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=62907
    title MS12-075: Vulnerability in Windows Kernel-Mode Drivers Could Allow Remote Code Execution (2761226)
  • 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
oval via4
accepted 2014-08-18T04:01:26.144-04:00
class vulnerability
contributors
  • name SecPod Team
    organization SecPod Technologies
  • name Pradeep R B
    organization SecPod Technologies
  • name Sharath S
    organization SecPod Technologies
  • name Maria Kedovskaya
    organization ALTX-SOFT
  • name Maria Mikhno
    organization ALTX-SOFT
definition_extensions
  • comment Microsoft Windows 7 is installed
    oval oval:org.mitre.oval:def:12541
  • comment Google Chrome is installed
    oval oval:org.mitre.oval:def:11914
  • comment Microsoft Windows XP (32-bit) is installed
    oval oval:org.mitre.oval:def:1353
  • comment Microsoft Windows XP x64 is installed
    oval oval:org.mitre.oval:def:15247
  • comment Microsoft Windows Server 2003 (32-bit) is installed
    oval oval:org.mitre.oval:def:1870
  • comment Microsoft Windows Server 2003 (x64) is installed
    oval oval:org.mitre.oval:def:730
  • comment Microsoft Windows Server 2003 (ia64) Gold is installed
    oval oval:org.mitre.oval:def:396
  • comment Microsoft Windows Vista (32-bit) is installed
    oval oval:org.mitre.oval:def:1282
  • comment Microsoft Windows Vista x64 Edition is installed
    oval oval:org.mitre.oval:def:2041
  • comment Microsoft Windows Server 2008 (32-bit) is installed
    oval oval:org.mitre.oval:def:4870
  • comment Microsoft Windows Server 2008 (64-bit) is installed
    oval oval:org.mitre.oval:def:5356
  • comment Microsoft Windows Server 2008 (ia-64) is installed
    oval oval:org.mitre.oval:def:5667
  • comment Microsoft Windows 7 is installed
    oval oval:org.mitre.oval:def:12541
  • comment Microsoft Windows Server 2008 R2 x64 Edition is installed
    oval oval:org.mitre.oval:def:6438
  • comment Microsoft Windows Server 2008 R2 Itanium-Based Edition is installed
    oval oval:org.mitre.oval:def:5954
  • comment Microsoft Windows 7 (32-bit) is installed
    oval oval:org.mitre.oval:def:6165
  • comment Microsoft Windows 7 x64 Edition is installed
    oval oval:org.mitre.oval:def:5950
  • comment Microsoft Windows Server 2008 R2 x64 Edition is installed
    oval oval:org.mitre.oval:def:6438
  • comment Microsoft Windows Server 2008 R2 Itanium-Based Edition is installed
    oval oval:org.mitre.oval:def:5954
  • comment Microsoft Windows 8 is installed
    oval oval:org.mitre.oval:def:15732
  • comment Microsoft Windows Server 2012 is installed
    oval oval:org.mitre.oval:def:16359
description The kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, Windows 7 Gold and SP1, Windows 8, Windows Server 2012, and Windows RT, as used by Google Chrome before 22.0.1229.79 and other programs, do not properly handle objects in memory, which allows remote attackers to execute arbitrary code via a crafted TrueType font file, aka "Windows Font Parsing Vulnerability" or "TrueType Font Parsing Vulnerability."
family windows
id oval:org.mitre.oval:def:15847
status accepted
submitted 2012-11-16T13:02:53
title TrueType Font Parsing Vulnerability - MS12-075
version 105
refmap via4
cert TA12-318A
confirm
ms MS12-075
sectrack 1027750
secunia 51239
xf google-chrome-cve20122897(78822)
Last major update 02-11-2013 - 23:24
Published 26-09-2012 - 06:56
Last modified 26-02-2019 - 09:04
Back to Top