ID CVE-2014-3198
Summary The Instance::HandleInputEvent function in pdf/instance.cc in the PDFium component in Google Chrome before 38.0.2125.101 interprets a certain -1 value as an index instead of a no-visible-page error code, which allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified vectors.
References
Vulnerable Configurations
  • cpe:2.3:a:google:chrome:38.0.2125.7
    cpe:2.3:a:google:chrome:38.0.2125.7
  • Red Hat Enterprise Linux Desktop Supplementary 6.0 (v. 6)
    cpe:2.3:o:redhat:enterprise_linux_desktop_supplementary:6.0
  • cpe:2.3:o:redhat:enterprise_linux_server_supplementary_eus:6.6.z
    cpe:2.3:o:redhat:enterprise_linux_server_supplementary_eus:6.6.z
  • Red Hat Enterprise Linux Workstation Supplementary 6.0 (v. 6)
    cpe:2.3:o:redhat:enterprise_linux_workstation_supplementary:6.0
  • Red Hat Enterprise Linux Server Supplementary 6.0 (v. 6)
    cpe:2.3:o:redhat:enterprise_linux_server_supplementary:6.0
CVSS
Base: 5.0 (as of 06-09-2016 - 21:43)
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 SuSE Local Security Checks
    NASL id OPENSUSE-2014-634.NASL
    description - Update to Chromium 38.0.2125.101 This update includes 159 security fixes, including 113 relatively minor fixes. Highlighted securtiy fixes are: CVE-2014-3188: A combination of V8 and IPC bugs that can lead to remote code execution outside of the sandbox CVE-2014-3189: Out-of-bounds read in PDFium CVE-2014-3190: Use-after-free in Events CVE-2014-3191: Use-after-free in Rendering CVE-2014-3192: Use-after-free in DOM CVE-2014-3193: Type confusion in Session Management CVE-2014-3194: Use-after-free in Web Workers CVE-2014-3195: Information Leak in V8 CVE-2014-3196: Permissions bypass in Windows Sandbox CVE-2014-3197: Information Leak in XSS Auditor CVE-2014-3198: Out-of-bounds read in PDFium CVE-2014-3199: Release Assert in V8 bindings CVE-2014-3200: Various fixes from internal audits, fuzzing and other initiatives - Drop the build of the Native Client. This is actually not a build as that prebuild binaries are being shipped. Also Google no longer provides prebuild binaries for the NativeClient for 32bit. Chromium as webbrowser is not affected by this and it bring Chromium inline with the regulations that prebuild binaries should not be shipped. - toolchaing_linux tarball dropped - Spec-file cleaned for NaCl stuff - Added patch no-clang-on-packman.diff to prevent the usage of clang on packman, which is not supported there
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 79267
    published 2014-11-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79267
    title openSUSE Security Update : chromium (openSUSE-SU-2014:1378-1)
  • NASL family Windows
    NASL id GOOGLE_CHROME_38_0_2125_101.NASL
    description The version of Google Chrome installed on the remote host is a version prior to 37.0.2062.94. It is, therefore, affected by the following vulnerabilities : - A flaw exists in V8 and IPC that can lead to remote code execution. (CVE-2014-3188) - Out-of-bounds read errors exist in PDFium. (CVE-2014-3189, CVE-2014-3198) - Use-after-free errors exist in Events, Rendering, DOM, and Web Workers. (CVE-2014-3190, CVE-2014-3191, CVE-2014-3192, CVE-2014-3194) - A type confusion error exists in Session Management. (CVE-2014-3193) - Information leak vulnerabilities exist in the V8 JavaScript engine and the XSS Auditor. (CVE-2014-3195, CVE-2014-3197) - A security bypass vulnerability exists in the Windows Sandbox. (CVE-2014-3196) - An error exists related to assertion of bindings in the V8 JavaScript engine. (CVE-2014-3199) - Multiple unspecified vulnerabilities exist. (CVE-2014-3200) - Multiple vulnerabilities in V8 exist.
    last seen 2019-02-21
    modified 2018-07-12
    plugin id 78080
    published 2014-10-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=78080
    title Google Chrome < 38.0.2125.101 Multiple Vulnerabilities
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201412-13.NASL
    description The remote host is affected by the vulnerability described in GLSA-201412-13 (Chromium: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Chromium. Please review the CVE identifiers referenced below for details. Impact : A remote attacker may be able to execute arbitrary code with the privileges of the process or cause a Denial of Service condition. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2015-04-13
    plugin id 79966
    published 2014-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79966
    title GLSA-201412-13 : Chromium: Multiple vulnerabilities
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2014-1626.NASL
    description Updated chromium-browser packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6 Supplementary. Red Hat Product Security has rated this update as having Critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. Chromium is an open source web browser, powered by WebKit (Blink). Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause Chromium to crash or, potentially, execute arbitrary code with the privileges of the user running Chromium. (CVE-2014-3188, CVE-2014-3189, CVE-2014-3190, CVE-2014-3191, CVE-2014-3192, CVE-2014-3193, CVE-2014-3194, CVE-2014-3199, CVE-2014-3200) Several information leak flaws were found in the processing of malformed web content. A web page containing malicious content could cause Chromium to disclose potentially sensitive information. (CVE-2014-3195, CVE-2014-3197, CVE-2014-3198) All Chromium users should upgrade to these updated packages, which contain Chromium version 38.0.2125.101, which corrects these issues. After installing the update, Chromium must be restarted for the changes to take effect.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 78415
    published 2014-10-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=78415
    title RHEL 6 : chromium-browser (RHSA-2014:1626)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_D2BBCC014EC311E4AB3F00262D5ED8EE.NASL
    description Google Chrome Releases reports : 159 security fixes in this release, including 113 found using MemorySanitizer : - [416449] Critical CVE-2014-3188: A special thanks to Juri Aedla for a combination of V8 and IPC bugs that can lead to remote code execution outside of the sandbox. - [398384] High CVE-2014-3189: Out-of-bounds read in PDFium. Credit to cloudfuzzer. - [400476] High CVE-2014-3190: Use-after-free in Events. Credit to cloudfuzzer. - [402407] High CVE-2014-3191: Use-after-free in Rendering. Credit to cloudfuzzer. - [403276] High CVE-2014-3192: Use-after-free in DOM. Credit to cloudfuzzer. - [399655] High CVE-2014-3193: Type confusion in Session Management. Credit to miaubiz. - [401115] High CVE-2014-3194: Use-after-free in Web Workers. Credit to Collin Payne. - [403409] Medium CVE-2014-3195: Information Leak in V8. Credit to Juri Aedla. - [338538] Medium CVE-2014-3196: Permissions bypass in Windows Sandbox. Credit to James Forshaw. - [396544] Medium CVE-2014-3197: Information Leak in XSS Auditor. Credit to Takeshi Terada. - [415307] Medium CVE-2014-3198: Out-of-bounds read in PDFium. Credit to Atte Kettunen of OUSPG. - [395411] Low CVE-2014-3199: Release Assert in V8 bindings. Credit to Collin Payne. - [420899] CVE-2014-3200: Various fixes from internal audits, fuzzing and other initiatives (Chrome 38). - Multiple vulnerabilities in V8 fixed at the tip of the 3.28 branch (currently 3.28.71.15).
    last seen 2019-02-21
    modified 2016-05-26
    plugin id 78104
    published 2014-10-09
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=78104
    title FreeBSD : chromium -- multiple vulnerabilities (d2bbcc01-4ec3-11e4-ab3f-00262d5ed8ee)
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_GOOGLE_CHROME_38_0_2125_101.NASL
    description The version of Google Chrome installed on the remote Mac OS X host is a version prior to 37.0.2062.94. It is, therefore, affected by the following vulnerabilities : - A flaw exists in V8 and IPC that can lead to remote code execution. (CVE-2014-3188) - Out-of-bounds read errors exist in PDFium. (CVE-2014-3189, CVE-2014-3198) - Use-after-free errors exist in Events, Rendering, DOM, and Web Workers. (CVE-2014-3190, CVE-2014-3191, CVE-2014-3192, CVE-2014-3194) - A type confusion error exists in Session Management. (CVE-2014-3193) - Information leak vulnerabilities exist in the V8 JavaScript engine and the XSS Auditor. (CVE-2014-3195, CVE-2014-3197) - A security bypass vulnerability exists in the Windows Sandbox. (CVE-2014-3196) - An error exists related to assertion of bindings in the V8 JavaScript engine. (CVE-2014-3199) - Multiple unspecified vulnerabilities exist. (CVE-2014-3200)
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 78081
    published 2014-10-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=78081
    title Google Chrome < 38.0.2125.101 Multiple Vulnerabilities (Mac OS X)
redhat via4
advisories
rhsa
id RHSA-2014:1626
refmap via4
bid 70273
confirm
Last major update 28-11-2016 - 14:11
Published 08-10-2014 - 06:55
Back to Top