ID CVE-2014-3189
Summary The chrome_pdf::CopyImage function in pdf/draw_utils.cc in the PDFium component in Google Chrome before 38.0.2125.101 does not properly validate image-data dimensions, which allows remote attackers to cause a denial of service (out-of-bounds read) or possibly have unspecified other impact via unknown 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: 7.5 (as of 06-09-2016 - 21:58)
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 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