Use-after-free vulnerability in core/dom/Node.cpp in Blink, as used in Google Chrome before 37.0.2062.120, allows remote attackers to cause a denial of service or possibly have unspecified other impact by leveraging improper handling of render-tree inconsistencies.

- 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

Multiple use-after-free issues were discovered in Blink. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit these to cause a denial of service via renderer crash, or execute arbitrary code with the privileges of the sandboxed render process. (CVE-2014-3178, CVE-2014-3190, CVE-2014-3191, CVE-2014-3192)

Multiple security issues were discovered in Chromium. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit these to read uninitialized memory, cause a denial of service via application crash or execute arbitrary code with the privileges of the user invoking the program. (CVE-2014-3179, CVE-2014-3200)

It was discovered that Chromium did not properly handle the interaction of IPC and V8. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to execute arbitrary code with the privileges of the user invoking the program. (CVE-2014-3188)

A use-after-free was discovered in the web workers implementation in Chromium. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via applicatin crash or execute arbitrary code with the privileges of the user invoking the program. (CVE-2014-3194)

It was discovered that V8 did not correctly handle JavaScript heap allocations in some circumstances. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to steal sensitive information. (CVE-2014-3195)

It was discovered that Blink did not properly provide substitute data for pages blocked by the XSS auditor. If a user were tricked in to opening a specially crafter website, an attacker could potentially exploit this to steal sensitive information. (CVE-2014-3197)

It was discovered that the wrap function for Event's in the V8 bindings in Blink produced an erroneous result in some circumstances.
If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service by stopping a worker process that was handling an Event object.
(CVE-2014-3199)

Multiple security issues were discovered in V8. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit these to read uninitialized memory, cause a denial of service via renderer crash or execute arbitrary code with the privileges of the sandboxed render process. (CVE-2014-7967).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Several vulnerabilities were discovered in the chromium web browser.

  - CVE-2014-3160     Christian Schneider discovered a same origin bypass     issue in SVG file resource fetching.

  - CVE-2014-3162     The Google Chrome development team addressed multiple     issues with potential security impact for chromium     36.0.1985.125.

  - CVE-2014-3165     Colin Payne discovered a use-after-free issue in the Web     Sockets implementation.

  - CVE-2014-3166     Antoine Delignat-Lavaud discovered an information leak     in the SPDY protocol implementation.

  - CVE-2014-3167     The Google Chrome development team addressed multiple     issues with potential security impact for chromium     36.0.1985.143.

  - CVE-2014-3168     cloudfuzzer discovered a use-after-free issue in SVG     image file handling.

  - CVE-2014-3169     Andrzej Dyjak discovered a use-after-free issue in the     Webkit/Blink Document Object Model implementation.

  - CVE-2014-3170     Rob Wu discovered a way to spoof the url of chromium     extensions.

  - CVE-2014-3171     cloudfuzzer discovered a use-after-free issue in     chromium's v8 bindings.

  - CVE-2014-3172     Eli Grey discovered a way to bypass access restrictions     using chromium's Debugger extension API.

  - CVE-2014-3173     jmuizelaar discovered an uninitialized read issue in     WebGL.

  - CVE-2014-3174     Atte Kettunen discovered an uninitialized read issue in     Web Audio.

  - CVE-2014-3175     The Google Chrome development team addressed multiple     issues with potential security impact for chromium     37.0.2062.94.

  - CVE-2014-3176     lokihardt@asrt discovered a combination of flaws that     can lead to remote code execution outside of chromium's     sandbox.

  - CVE-2014-3177     lokihardt@asrt discovered a combination of flaws that     can lead to remote code execution outside of chromium's     sandbox.

  - CVE-2014-3178     miaubiz discovered a use-after-free issue in the     Document Object Model implementation in Blink/Webkit.

  - CVE-2014-3179     The Google Chrome development team addressed multiple     issues with potential security impact for chromium     37.0.2062.120.

The remote host is affected by the vulnerability described in GLSA-201409-06 (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 cause a Denial of Service condition or       possibly have other unspecified impact by leveraging improper handling of       render-tree inconsistencies.
  Workaround :

    There is no known workaround at this time.

The version of Google Chrome installed on the remote host is a version prior to 37.0.2062.120 and is thus missing fixes for several vulnerabilities, one of which is a use-after-free error in the Blink rendering engine, which could be leveraged for remote code execution. Fixes for miscellaneous other vulnerabilities also exist in this latest version, and the integrated Flash engine has been updated to the concurrent 15.0.0.152 version as well.

Google Chrome Releases reports :

4 security fixes in this release, including :

- [401362] High CVE-2014-3178: Use-after-free in rendering. Credit to miaubiz.

- [411014] CVE-2014-3179: Various fixes from internal audits, fuzzing and other initiatives.

The version of Google Chrome installed on the remote Mac OS X host is a version prior to 37.0.2062.120. It is, therefore, affected by the following vulnerabilities :

  - A use-after-free error exists related to rendering that     allows a remote attacker to execute arbitrary code.
    (CVE-2014-3178)

  - Unspecified errors exist having unspecified impact.
    (CVE-2014-3179)

Note that the following issues exist due to the version of Adobe Flash bundled with the application :

  - Unspecified memory corruption issues exist that allow     arbitrary code execution. (CVE-2014-0547, CVE-2014-0549,     CVE-2014-0550, CVE-2014-0551, CVE-2014-0552,     CVE-2014-0555)

  - An unspecified error exists that allows cross-origin     policy violations. (CVE-2014-0548)

  - A use-after-free error exists that allows arbitrary     code execution. (CVE-2014-0553)

  - An unspecified error exists that allows an unspecified     security bypass. (CVE-2014-0554)

  - Unspecified errors exist that allow memory leaks leading     to easier defeat of memory address randomization.
    (CVE-2014-0557)

  - Heap-based buffer overflow errors exist that allow     arbitrary code execution. (CVE-2014-0556, CVE-2014-0559)

The version of Google Chrome installed on the remote host is a version prior to 37.0.2062.120. It is, therefore, affected by the following vulnerabilities :

  - A use-after-free error exists related to rendering that     allows a remote attacker to execute arbitrary code.
    (CVE-2014-3178)

  - Unspecified errors exist having unspecified impact.
    (CVE-2014-3179)

Note that the following issues exist due to the version of Adobe Flash bundled with the application :

  - Unspecified memory corruption issues exist that allow     arbitrary code execution. (CVE-2014-0547, CVE-2014-0549,     CVE-2014-0550, CVE-2014-0551, CVE-2014-0552,     CVE-2014-0555)

  - An unspecified error exists that allows cross-origin     policy violations. (CVE-2014-0548)

  - A use-after-free error exists that allows arbitrary     code execution. (CVE-2014-0553)

  - An unspecified error exists that allows an unspecified     security bypass. (CVE-2014-0554)

  - Unspecified errors exist that allow memory leaks leading     to easier defeat of memory address randomization.
    (CVE-2014-0557)

  - Heap-based buffer overflow errors exist that allow     arbitrary code execution. (CVE-2014-0556, CVE-2014-0559)

ID	Name	Product	Family	Severity
79267	openSUSE Security Update : chromium (openSUSE-SU-2014:1378-1)	Nessus	SuSE Local Security Checks	critical
78465	Ubuntu 14.04 LTS : Oxide vulnerabilities (USN-2345-1)	Nessus	Ubuntu Local Security Checks	high
77973	Debian DSA-3039-1 : chromium-browser - security update	Nessus	Debian Local Security Checks	critical
77774	GLSA-201409-06 : Chromium: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
8374	Google Chrome < 37.0.2062.120 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	high
77596	FreeBSD : www/chromium -- multiple vulnerabilities (36a415c8-3867-11e4-b522-00262d5ed8ee)	Nessus	FreeBSD Local Security Checks	high
77582	Google Chrome < 37.0.2062.120 Multiple Vulnerabilities (Mac OS X)	Nessus	MacOS X Local Security Checks	critical
77581	Google Chrome < 37.0.2062.120 Multiple Vulnerabilities	Nessus	Windows	critical

Detections

Analytics

CVE-2014-3178

critical

Tenable Plugins

critical

high

critical

high

high

high

critical

critical