ID CVE-2013-2864
Summary The PDF functionality in Google Chrome before 27.0.1453.110 allows remote attackers to cause a denial of service (invalid free operation) or possibly have unspecified other impact via unknown vectors.
References
Vulnerable Configurations
  • Google Chrome 27.0.1453.109
    cpe:2.3:a:google:chrome:27.0.1453.109
  • Google Chrome 27.0.1453.63
    cpe:2.3:a:google:chrome:27.0.1453.63
  • Google Chrome 27.0.1453.64
    cpe:2.3:a:google:chrome:27.0.1453.64
  • Google Chrome 27.0.1453.65
    cpe:2.3:a:google:chrome:27.0.1453.65
  • Google Chrome 27.0.1453.66
    cpe:2.3:a:google:chrome:27.0.1453.66
  • Google Chrome 27.0.1453.67
    cpe:2.3:a:google:chrome:27.0.1453.67
  • Google Chrome 27.0.1453.68
    cpe:2.3:a:google:chrome:27.0.1453.68
  • Google Chrome 27.0.1453.69
    cpe:2.3:a:google:chrome:27.0.1453.69
  • Google Chrome 27.0.1453.70
    cpe:2.3:a:google:chrome:27.0.1453.70
  • Google Chrome 27.0.1453.55
    cpe:2.3:a:google:chrome:27.0.1453.55
  • Google Chrome 27.0.1453.56
    cpe:2.3:a:google:chrome:27.0.1453.56
  • Google Chrome 27.0.1453.57
    cpe:2.3:a:google:chrome:27.0.1453.57
  • Google Chrome 27.0.1453.58
    cpe:2.3:a:google:chrome:27.0.1453.58
  • Google Chrome 27.0.1453.59
    cpe:2.3:a:google:chrome:27.0.1453.59
  • Google Chrome 27.0.1453.60
    cpe:2.3:a:google:chrome:27.0.1453.60
  • Google Chrome 27.0.1453.61
    cpe:2.3:a:google:chrome:27.0.1453.61
  • Google Chrome 27.0.1453.62
    cpe:2.3:a:google:chrome:27.0.1453.62
  • Google Chrome 27.0.1453.80
    cpe:2.3:a:google:chrome:27.0.1453.80
  • Google Chrome 27.0.1453.79
    cpe:2.3:a:google:chrome:27.0.1453.79
  • Google Chrome 27.0.1453.82
    cpe:2.3:a:google:chrome:27.0.1453.82
  • Google Chrome 27.0.1453.81
    cpe:2.3:a:google:chrome:27.0.1453.81
  • Google Chrome 27.0.1453.84
    cpe:2.3:a:google:chrome:27.0.1453.84
  • Google Chrome 27.0.1453.83
    cpe:2.3:a:google:chrome:27.0.1453.83
  • Google Chrome 27.0.1453.86
    cpe:2.3:a:google:chrome:27.0.1453.86
  • Google Chrome 27.0.1453.85
    cpe:2.3:a:google:chrome:27.0.1453.85
  • Google Chrome 27.0.1453.72
    cpe:2.3:a:google:chrome:27.0.1453.72
  • Google Chrome 27.0.1453.71
    cpe:2.3:a:google:chrome:27.0.1453.71
  • Google Chrome 27.0.1453.74
    cpe:2.3:a:google:chrome:27.0.1453.74
  • Google Chrome 27.0.1453.73
    cpe:2.3:a:google:chrome:27.0.1453.73
  • Google Chrome 27.0.1453.76
    cpe:2.3:a:google:chrome:27.0.1453.76
  • Google Chrome 27.0.1453.75
    cpe:2.3:a:google:chrome:27.0.1453.75
  • Google Chrome 27.0.1453.78
    cpe:2.3:a:google:chrome:27.0.1453.78
  • Google Chrome 27.0.1453.77
    cpe:2.3:a:google:chrome:27.0.1453.77
  • Google Chrome 27.0.1453.89
    cpe:2.3:a:google:chrome:27.0.1453.89
  • Google Chrome 27.0.1453.90
    cpe:2.3:a:google:chrome:27.0.1453.90
  • Google Chrome 27.0.1453.87
    cpe:2.3:a:google:chrome:27.0.1453.87
  • Google Chrome 27.0.1453.88
    cpe:2.3:a:google:chrome:27.0.1453.88
  • Google Chrome 27.0.1453.91
    cpe:2.3:a:google:chrome:27.0.1453.91
  • Google Chrome 27.0.1453.93
    cpe:2.3:a:google:chrome:27.0.1453.93
  • Google Chrome 27.0.1453.10
    cpe:2.3:a:google:chrome:27.0.1453.10
  • Google Chrome 27.0.1453.9
    cpe:2.3:a:google:chrome:27.0.1453.9
  • Google Chrome 27.0.1453.103
    cpe:2.3:a:google:chrome:27.0.1453.103
  • Google Chrome 27.0.1453.104
    cpe:2.3:a:google:chrome:27.0.1453.104
  • Google Chrome 27.0.1453.94
    cpe:2.3:a:google:chrome:27.0.1453.94
  • Google Chrome 27.0.1453.102
    cpe:2.3:a:google:chrome:27.0.1453.102
  • Google Chrome 27.0.1453.41
    cpe:2.3:a:google:chrome:27.0.1453.41
  • Google Chrome 27.0.1453.106
    cpe:2.3:a:google:chrome:27.0.1453.106
  • Google Chrome 27.0.1453.42
    cpe:2.3:a:google:chrome:27.0.1453.42
  • Google Chrome 27.0.1453.105
    cpe:2.3:a:google:chrome:27.0.1453.105
  • Google Chrome 27.0.1453.43
    cpe:2.3:a:google:chrome:27.0.1453.43
  • Google Chrome 27.0.1453.108
    cpe:2.3:a:google:chrome:27.0.1453.108
  • Google Chrome 27.0.1453.44
    cpe:2.3:a:google:chrome:27.0.1453.44
  • Google Chrome 27.0.1453.107
    cpe:2.3:a:google:chrome:27.0.1453.107
  • Google Chrome 27.0.1453.37
    cpe:2.3:a:google:chrome:27.0.1453.37
  • Google Chrome 27.0.1453.38
    cpe:2.3:a:google:chrome:27.0.1453.38
  • Google Chrome 27.0.1453.39
    cpe:2.3:a:google:chrome:27.0.1453.39
  • Google Chrome 27.0.1453.40
    cpe:2.3:a:google:chrome:27.0.1453.40
  • Google Chrome 27.0.1453.50
    cpe:2.3:a:google:chrome:27.0.1453.50
  • Google Chrome 27.0.1453.51
    cpe:2.3:a:google:chrome:27.0.1453.51
  • Google Chrome 27.0.1453.52
    cpe:2.3:a:google:chrome:27.0.1453.52
  • Google Chrome 27.0.1453.54
    cpe:2.3:a:google:chrome:27.0.1453.54
  • Google Chrome 27.0.1453.45
    cpe:2.3:a:google:chrome:27.0.1453.45
  • Google Chrome 27.0.1453.46
    cpe:2.3:a:google:chrome:27.0.1453.46
  • Google Chrome 27.0.1453.47
    cpe:2.3:a:google:chrome:27.0.1453.47
  • Google Chrome 27.0.1453.49
    cpe:2.3:a:google:chrome:27.0.1453.49
  • Google Chrome 27.0.1453.3
    cpe:2.3:a:google:chrome:27.0.1453.3
  • Google Chrome 27.0.1453.4
    cpe:2.3:a:google:chrome:27.0.1453.4
  • Google Chrome 27.0.1453.1
    cpe:2.3:a:google:chrome:27.0.1453.1
  • Google Chrome 27.0.1453.2
    cpe:2.3:a:google:chrome:27.0.1453.2
  • Google Chrome 27.0.1453.7
    cpe:2.3:a:google:chrome:27.0.1453.7
  • Google Chrome 27.0.1453.8
    cpe:2.3:a:google:chrome:27.0.1453.8
  • Google Chrome 27.0.1453.5
    cpe:2.3:a:google:chrome:27.0.1453.5
  • Google Chrome 27.0.1453.6
    cpe:2.3:a:google:chrome:27.0.1453.6
  • Google Chrome 27.0.1453.34
    cpe:2.3:a:google:chrome:27.0.1453.34
  • Google Chrome 27.0.1453.15
    cpe:2.3:a:google:chrome:27.0.1453.15
  • Google Chrome 27.0.1453.36
    cpe:2.3:a:google:chrome:27.0.1453.36
  • Google Chrome 27.0.1453.35
    cpe:2.3:a:google:chrome:27.0.1453.35
  • Google Chrome 27.0.1453.11
    cpe:2.3:a:google:chrome:27.0.1453.11
  • Google Chrome 27.0.1453.0
    cpe:2.3:a:google:chrome:27.0.1453.0
  • Google Chrome 27.0.1453.13
    cpe:2.3:a:google:chrome:27.0.1453.13
  • Google Chrome 27.0.1453.12
    cpe:2.3:a:google:chrome:27.0.1453.12
CVSS
Base: 7.5 (as of 18-10-2016 - 07:40)
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
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family Windows
    NASL id GOOGLE_CHROME_27_0_1453_110.NASL
    description The version of Google Chrome installed on the remote host is a version prior to 27.0.1453.110 and is, therefore, affected by the following vulnerabilities : - An error exists related to the renderer and bad handles. (CVE-2013-2854) - Errors exist related to dev tools API, Skia GPU handling and SSL socket handling that could result in memory corruption. (CVE-2013-2855, CVE-2013-2862, CVE-2013-2863) - Use-after-free errors exist related to input and image handling, HTML5 audio, workers accessing database APIs and SVG processing. (CVE-2013-2856, CVE-2013-2857, CVE-2013-2858, CVE-2013-2860, CVE-2013-2861) - An unspecified error exists that could allow cross- origin namespace pollution. (CVE-2013-2859) - An error exists in the PDF viewer that could allow bad free operations. (CVE-2013-2864) - The vendor reports various, unspecified errors exist. (CVE-2013-2865)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 66813
    published 2013-06-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=66813
    title Google Chrome < 27.0.1453.110 Multiple Vulnerabilities
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_4865D189CD6211E2AE1100262D5ED8EE.NASL
    description Google Chrome Releases reports : [242322] Medium CVE-2013-2855: Memory corruption in dev tools API. Credit to 'daniel.zulla'. [242224] High CVE-2013-2856: Use-after-free in input handling. Credit to miaubiz. [240124] High CVE-2013-2857: Use-after-free in image handling. Credit to miaubiz. [239897] High CVE-2013-2858: Use-after-free in HTML5 Audio. Credit to 'cdel921'. [237022] High CVE-2013-2859: Cross-origin namespace pollution. to 'bobbyholley'. [225546] High CVE-2013-2860: Use-after-free with workers accessing database APIs. Credit to Collin Payne. [209604] High CVE-2013-2861: Use-after-free with SVG. Credit to miaubiz. [161077] High CVE-2013-2862: Memory corruption in Skia GPU handling. Credit to Atte Kettunen of OUSPG. [232633] Critical CVE-2013-2863: Memory corruption in SSL socket handling. Credit to Sebastian Marchand of the Chromium development community. [239134] High CVE-2013-2864: Bad free in PDF viewer. Credit to Mateusz Jurczyk, with contributions by Gynvael Coldwind, both from Google Security Team. [246389] High CVE-2013-2865: Various fixes from internal audits, fuzzing and other initiatives.
    last seen 2019-02-21
    modified 2013-06-29
    plugin id 66799
    published 2013-06-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=66799
    title FreeBSD : chromium -- multiple vulnerabilities (4865d189-cd62-11e2-ae11-00262d5ed8ee)
oval via4
accepted 2013-08-12T04:08:46.256-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 The PDF functionality in Google Chrome before 27.0.1453.110 allows remote attackers to cause a denial of service (invalid free operation) or possibly have unspecified other impact via unknown vectors.
family windows
id oval:org.mitre.oval:def:16736
status accepted
submitted 2013-06-04T22:14:11.849-04:00
title The PDF functionality in Google Chrome before 27.0.1453.110 allows remote attackers to cause a denial of service (invalid free operation) or possibly have unspecified other impact via unknown vectors
version 42
refmap via4
confirm
Last major update 18-10-2016 - 11:13
Published 04-06-2013 - 20:55
Last modified 18-09-2017 - 21:36
Back to Top