The Autofill implementation in Google Chrome before 51.0.2704.79 mishandles the interaction between field updates and JavaScript code that triggers a frame deletion, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted web site, a different vulnerability than CVE-2016-1690.

Chromium was updated to 51.0.2704.79 to fix a number of security issues. [boo#982719]

  - CVE-2016-1696: Cross-origin bypass in Extension bindings

  - CVE-2016-1697: Cross-origin bypass in Blink

  - CVE-2016-1698: Information leak in Extension bindings

  - CVE-2016-1699: Parameter sanitization failure in     DevTools

  - CVE-2016-1700: Use-after-free in Extensions

  - CVE-2016-1701: Use-after-free in Autofill

  - CVE-2016-1702: Out-of-bounds read in Skia

  - CVE-2016-1703: Various fixes from internal audits,     fuzzing and other initiatives

Google Chrome Releases reports :

15 security fixes in this release, including :

- 601073] High CVE-2016-1696: Cross-origin bypass in Extension bindings. Credit to anonymous.

- [613266] High CVE-2016-1697: Cross-origin bypass in Blink. Credit to Mariusz Mlynski.

- [603725] Medium CVE-2016-1698: Information leak in Extension bindings. Credit to Rob Wu.

- [607939] Medium CVE-2016-1699: Parameter sanitization failure in DevTools. Credit to Gregory Panakkal.

- [608104] Medium CVE-2016-1700: Use-after-free in Extensions. Credit to Rob Wu.

- [608101] Medium CVE-2016-1701: Use-after-free in Autofill. Credit to Rob Wu.

- [609260] Medium CVE-2016-1702: Out-of-bounds read in Skia. Credit to cloudfuzzer.

- [616539] CVE-2016-1703: Various fixes from internal audits, fuzzing and other initiatives.

Chromium was updated to 51.0.2704.79 to fix the following vulnerabilities :

  - CVE-2016-1696: Cross-origin bypass in Extension bindings

  - CVE-2016-1697: Cross-origin bypass in Blink

  - CVE-2016-1698: Information leak in Extension bindings

  - CVE-2016-1699: Parameter sanitization failure in     DevTools

  - CVE-2016-1700: Use-after-free in Extensions

  - CVE-2016-1701: Use-after-free in Autofill

  - CVE-2016-1702: Out-of-bounds read in Skia

  - CVE-2016-1703: Various fixes from internal audits,     fuzzing and other initiatives Also includes     vulnerabilities fixed in 51.0.2704.63 (boo#981886) :

  - CVE-2016-1672: Cross-origin bypass in extension bindings

  - CVE-2016-1673: Cross-origin bypass in Blink

  - CVE-2016-1674: Cross-origin bypass in extensions

  - CVE-2016-1675: Cross-origin bypass in Blink

  - CVE-2016-1676: Cross-origin bypass in extension bindings

  - CVE-2016-1677: Type confusion in V8

  - CVE-2016-1678: Heap overflow in V8

  - CVE-2016-1679: Heap use-after-free in V8 bindings

  - CVE-2016-1680: Heap use-after-free in Skia

  - CVE-2016-1681: Heap overflow in PDFium

  - CVE-2016-1682: CSP bypass for ServiceWorker

  - CVE-2016-1683: Out-of-bounds access in libxslt

  - CVE-2016-1684: Integer overflow in libxslt

  - CVE-2016-1685: Out-of-bounds read in PDFium

  - CVE-2016-1686: Out-of-bounds read in PDFium

  - CVE-2016-1687: Information leak in extensions

  - CVE-2016-1688: Out-of-bounds read in V8

  - CVE-2016-1689: Heap buffer overflow in media

  - CVE-2016-1690: Heap use-after-free in Autofill

  - CVE-2016-1691: Heap buffer-overflow in Skia

  - CVE-2016-1692: Limited cross-origin bypass in     ServiceWorker

  - CVE-2016-1693: HTTP Download of Software Removal Tool

  - CVE-2016-1694: HPKP pins removed on cache clearance

  - CVE-2016-1695: Various fixes from internal audits,     fuzzing and other initiatives

Several vulnerabilities have been discovered in the chromium web browser.

  - CVE-2016-1696     A cross-origin bypass was found in the bindings to     extensions.

  - CVE-2016-1697     Mariusz Mlynski discovered a cross-origin bypass in     Blink/Webkit.

  - CVE-2016-1698     Rob Wu discovered an information leak.

  - CVE-2016-1699     Gregory Panakkal discovered an issue in the Developer     Tools feature.

  - CVE-2016-1700     Rob Wu discovered a use-after-free issue in extensions.

  - CVE-2016-1701     Rob Wu discovered a use-after-free issue in the autofill     feature.

  - CVE-2016-1702     cloudfuzzer discovered an out-of-bounds read issue in     the skia library.

The version of Google Chrome installed on the remote macOS host is prior to 51.0.2704.79. It is, therefore, affected by multiple vulnerabilities as referenced in the 2016_06_stable-channel-update advisory.

  - Multiple unspecified vulnerabilities in Google Chrome before 51.0.2704.79 allow attackers to cause a     denial of service or possibly have other impact via unknown vectors. (CVE-2016-1703)

  - The extensions subsystem in Google Chrome before 51.0.2704.79 does not properly restrict bindings access,     which allows remote attackers to bypass the Same Origin Policy via unspecified vectors. (CVE-2016-1696)

  - The FrameLoader::startLoad function in WebKit/Source/core/loader/FrameLoader.cpp in Blink, as used in     Google Chrome before 51.0.2704.79, does not prevent frame navigations during DocumentLoader detach     operations, which allows remote attackers to bypass the Same Origin Policy via crafted JavaScript code.
    (CVE-2016-1697)

  - The createCustomType function in extensions/renderer/resources/binding.js in the extension bindings in     Google Chrome before 51.0.2704.79 does not validate module types, which might allow attackers to load     arbitrary modules or obtain sensitive information by leveraging a poisoned definition. (CVE-2016-1698)

  - WebKit/Source/devtools/front_end/devtools.js in the Developer Tools (aka DevTools) subsystem in Blink, as     used in Google Chrome before 51.0.2704.79, does not ensure that the remoteFrontendUrl parameter is     associated with a chrome-devtools-frontend.appspot.com URL, which allows remote attackers to bypass     intended access restrictions via a crafted URL. (CVE-2016-1699)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Google Chrome installed on the remote Windows host is prior to 51.0.2704.79. It is, therefore, affected by multiple vulnerabilities as referenced in the 2016_06_stable-channel-update advisory.

  - Multiple unspecified vulnerabilities in Google Chrome before 51.0.2704.79 allow attackers to cause a     denial of service or possibly have other impact via unknown vectors. (CVE-2016-1703)

  - The extensions subsystem in Google Chrome before 51.0.2704.79 does not properly restrict bindings access,     which allows remote attackers to bypass the Same Origin Policy via unspecified vectors. (CVE-2016-1696)

  - The FrameLoader::startLoad function in WebKit/Source/core/loader/FrameLoader.cpp in Blink, as used in     Google Chrome before 51.0.2704.79, does not prevent frame navigations during DocumentLoader detach     operations, which allows remote attackers to bypass the Same Origin Policy via crafted JavaScript code.
    (CVE-2016-1697)

  - The createCustomType function in extensions/renderer/resources/binding.js in the extension bindings in     Google Chrome before 51.0.2704.79 does not validate module types, which might allow attackers to load     arbitrary modules or obtain sensitive information by leveraging a poisoned definition. (CVE-2016-1698)

  - WebKit/Source/devtools/front_end/devtools.js in the Developer Tools (aka DevTools) subsystem in Blink, as     used in Google Chrome before 51.0.2704.79, does not ensure that the remoteFrontendUrl parameter is     associated with a chrome-devtools-frontend.appspot.com URL, which allows remote attackers to bypass     intended access restrictions via a crafted URL. (CVE-2016-1699)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

An update for chromium-browser is now available for Red Hat Enterprise Linux 6 Supplementary.

Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Chromium is an open source web browser, powered by WebKit (Blink).

This update upgrades Chromium to version 51.0.2704.79.

Security Fix(es) :

* Multiple flaws were found in the processing of malformed web content. A web page containing malicious content could cause Chromium to crash, execute arbitrary code, or disclose sensitive information when visited by the victim. (CVE-2016-1696, CVE-2016-1697, CVE-2016-1703, CVE-2016-1698, CVE-2016-1699, CVE-2016-1700, CVE-2016-1701, CVE-2016-1702)

ID	Name	Product	Family	Type	Severity
91492	openSUSE Security Update : Chromium (openSUSE-2016-1489)	Nessus	SuSE Local Security Checks	Local	high
91491	FreeBSD : chromium -- multiple vulnerabilities (c039a761-2c29-11e6-8912-3065ec8fd3ec)	Nessus	FreeBSD Local Security Checks	Local	high
91485	openSUSE Security Update : Chromium (openSUSE-2016-682)	Nessus	SuSE Local Security Checks	Local	high
91473	Debian DSA-3594-1 : chromium-browser - security update	Nessus	Debian Local Security Checks	Local	high
91456	Google Chrome < 51.0.2704.79 Multiple Vulnerabilities	Nessus	MacOS X Local Security Checks	Local	high
91455	Google Chrome < 51.0.2704.79 Multiple Vulnerabilities	Nessus	Windows	Local	high
91449	RHEL 6 : chromium-browser (RHSA-2016:1201)	Nessus	Red Hat Local Security Checks	Local	high

Detections

Analytics

CVE-2016-1701

high

Tenable Plugins

high

high

high

high

high

high

high