The remote host is affected by the vulnerability described in GLSA-201605-02 (Chromium: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in the Chromium web       browser. Please review the CVE identifiers referenced below for details.
  Impact :

    A remote attacker could possibly execute arbitrary code with the       privileges of the process, cause a Denial of Service condition, obtain       sensitive information, or bypass security restrictions.
  Workaround :

    There is no known workaround at this time.

Google Chrome Releases reports :

9 security fixes in this release, including :

- [574802] High CVE-2016-1660: Out-of-bounds write in Blink. Credit to Atte Kettunen of OUSPG.

- [601629] High CVE-2016-1661: Memory corruption in cross-process frames. Credit to Wadih Matar.

- [603732] High CVE-2016-1662: Use-after-free in extensions. Credit to Rob Wu.

- [603987] High CVE-2016-1663: Use-after-free in Blink's V8 bindings.
Credit to anonymous.

- [597322] Medium CVE-2016-1664: Address bar spoofing. Credit to Wadih Matar.

- [606181] Medium CVE-2016-1665: Information leak in V8. Credit to HyungSeok Han.

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

Chromium was updated to 50.0.2661.94 to fix a number of vulnerabilities (boo#977830) :

  - CVE-2016-1660: Out-of-bounds write in Blink

  - CVE-2016-1661: Memory corruption in cross-process frames

  - CVE-2016-1662: Use-after-free in extensions

  - CVE-2016-1663: Use-after-free in Blink&rsquo;s V8     bindings

  - CVE-2016-1664: Address bar spoofing

  - CVE-2016-1665: Information leak in V8

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

The version of Google Chrome installed on the remote Windows host is prior to 50.0.2661.94. It is, therefore, affected by multiple vulnerabilities :

  - An out-of-bounds write error exists in Blink that allows     a context-dependent attacker to execute arbitrary code.
    (CVE-2016-1660)

  - A flaw exists due to improper validation of     user-supplied input when handling cross-process frames.
    A context-dependent attacker can exploit this to corrupt     memory, resulting in the execution of arbitrary code.
    (CVE-2016-1661)

  - A use-after-free error exists in the extensions     component. A context-dependent attacker can exploit this     to dereference already freed memory, resulting in the     execution of arbitrary code. (CVE-2016-1662)

  - A use-after-free free error exists in Blink's V8     bindings. A context-dependent attacker can exploit this     to dereference already freed memory, resulting in the     execution of arbitrary code. (CVE-2016-1663)

  - An unspecified flaw exists that allows a     context-dependent attacker to spoof the address bar.
    (CVE-2016-1664)

  - An unspecified flaw exists in V8 that allows a     context-dependent attacker to disclose sensitive     information. (CVE-2016-1665)

  - Multiple unspecified vulnerabilities exist that allow a     a context-dependent attacker to execute arbitrary code.
    (CVE-2016-1666)

  - A same-origin bypass vulnerability exists in Skia in the     pinToByte() function in effects/SkArithmeticMode.cpp due     to improper handling of intermediate color values. An     unauthenticated, remote attacker can exploit this, via     timing attacks using the SVG 'feComposite' filter, to     bypass the same-origin policy. (CVE-2016-5168)

Several vulnerabilities have been discovered in the chromium web browser.

  - CVE-2016-1660     Atte Kettunen discovered an out-of-bounds write issue.

  - CVE-2016-1661     Wadih Matar discovered a memory corruption issue.

  - CVE-2016-1662     Rob Wu discovered a use-after-free issue related to     extensions.

  - CVE-2016-1663     A use-after-free issue was discovered in Blink's     bindings to V8.

  - CVE-2016-1664     Wadih Matar discovered a way to spoof URLs.

  - CVE-2016-1665     gksgudtjr456 discovered an information leak in the v8     JavaScript library.

  - CVE-2016-1666     The chrome development team found and fixed various     issues during internal auditing.

Chromium was updated to 51.0.2704.103 to fix three vulnerabilities :

  - CVE-2016-1704: Various fixes from internal audits,     fuzzing and other initiatives (shared identifier)     (boo#985397)

Includes vulnerability fixes from 50.0.2661.102 (boo#979859) :

  - CVE-2016-1667: Same origin bypass in DOM

  - CVE-2016-1668: Same origin bypass in Blink V8 bindings

  - CVE-2016-1669: Buffer overflow in V8

  - CVE-2016-1670: Race condition in loader

Includes vulnerability fixes from 50.0.2661.94 (boo#977830) :

  - CVE-2016-1660: Out-of-bounds write in Blink

  - CVE-2016-1661: Memory corruption in cross-process frames

  - CVE-2016-1662: Use-after-free in extensions

  - CVE-2016-1663: Use-after-free in Blink&rsquo;s V8     bindings

  - CVE-2016-1664: Address bar spoofing

  - CVE-2016-1665: Information leak in V8

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

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

  - An out-of-bounds write error exists in Blink that allows     a context-dependent attacker to execute arbitrary code.
    (CVE-2016-1660)

  - A flaw exists due to improper validation of     user-supplied input when handling cross-process frames.
    A context-dependent attacker can exploit this to corrupt     memory, resulting in the execution of arbitrary code.
    (CVE-2016-1661)

  - A use-after-free error exists in the extensions     component. A context-dependent attacker can exploit this     to dereference already freed memory, resulting in the     execution of arbitrary code. (CVE-2016-1662)

  - A use-after-free free error exists in Blink's V8     bindings. A context-dependent attacker can exploit this     to dereference already freed memory, resulting in the     execution of arbitrary code. (CVE-2016-1663)

  - An unspecified flaw exists that allows a     context-dependent attacker to spoof the address bar.
    (CVE-2016-1664)

  - An unspecified flaw exists in V8 that allows a     context-dependent attacker to disclose sensitive     information. (CVE-2016-1665)

  - Multiple unspecified vulnerabilities exist that allow a     a context-dependent attacker to execute arbitrary code.
    (CVE-2016-1666)

  - A same-origin bypass vulnerability exists in Skia in the     pinToByte() function in effects/SkArithmeticMode.cpp due     to improper handling of intermediate color values. An     unauthenticated, remote attacker can exploit this, via     timing attacks using the SVG 'feComposite' filter, to     bypass the same-origin policy. (CVE-2016-5168)

The remote Ubuntu 14.04 LTS / 16.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-2960-1 advisory.

    An out of bounds write was discovered in Blink. 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 renderer crash, or     execute arbitrary code. (CVE-2016-1660)

    It was discovered that Blink assumes that a frame which passes same-origin checks is local in some cases.
    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 renderer crash, or execute arbitrary code. (CVE-2016-1661)

    A use-after-free was discovered in the V8 bindings in Blink. 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     renderer crash, or execute arbitrary code. (CVE-2016-1663)

    It was discovered that the JSGenericLowering class in V8 mishandles comparison operators. If a user were     tricked in to opening a specially crafted website, an attacker could potentially exploit this to obtain     sensitive information. (CVE-2016-1665)

    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. (CVE-2016-1666)

    It was discovered that the TreeScope::adoptIfNeeded function in Blink does not prevent script execution     during node-adoption operations. If a user were tricked in to opening a specially crafted website, an     attacker could potentially exploit this to bypass same origin restrictions. (CVE-2016-1667)

    It was discovered that the forEachForBinding in the V8 bindings in Blink uses an improper creation     context. If a user were tricked in to opening a specially crafted website, an attacker could potentially     exploit this to bypass same origin restrictions. (CVE-2016-1668)

    A buffer overflow was discovered in V8. 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 renderer crash, or execute     arbitrary code. (CVE-2016-1669)

    A race condition was discovered in ResourceDispatcherHostImpl in Chromium. An attacker could potentially     exploit this to make arbitrary HTTP requests. (CVE-2016-1670)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

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 50.0.2661.94.

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-1660, CVE-2016-1661, CVE-2016-1662, CVE-2016-1663, CVE-2016-1666, CVE-2016-1664, CVE-2016-1665)

ID	Name	Product	Family	Published	Updated	Severity
91176	GLSA-201605-02 : Chromium: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	5/17/2016	6/8/2022	critical
91374	FreeBSD : chromium -- multiple vulnerabilities (7da1da96-24bb-11e6-bd31-3065ec8fd3ec)	Nessus	FreeBSD Local Security Checks	5/31/2016	1/4/2021	critical
90878	openSUSE Security Update : Chromium (openSUSE-2016-538)	Nessus	SuSE Local Security Checks	5/4/2016	1/19/2021	critical
90879	openSUSE Security Update : Chromium (openSUSE-2016-539)	Nessus	SuSE Local Security Checks	5/4/2016	1/19/2021	critical
90794	Google Chrome < 50.0.2661.94 Multiple Vulnerabilities	Nessus	Windows	4/29/2016	4/11/2022	critical
90840	Debian DSA-3564-1 : chromium-browser - security update	Nessus	Debian Local Security Checks	5/3/2016	1/11/2021	critical
91848	openSUSE Security Update : Chromium (openSUSE-2016-756)	Nessus	SuSE Local Security Checks	6/27/2016	1/19/2021	critical
90795	Google Chrome < 50.0.2661.94 Multiple Vulnerabilities (Mac OS X)	Nessus	MacOS X Local Security Checks	4/29/2016	11/19/2019	critical
91257	Ubuntu 14.04 LTS / 16.04 LTS : Oxide vulnerabilities (USN-2960-1)	Nessus	Ubuntu Local Security Checks	5/19/2016	8/27/2024	critical
90852	RHEL 6 : chromium-browser (RHSA-2016:0707)	Nessus	Red Hat Local Security Checks	5/3/2016	5/29/2020	critical

Detections

Analytics

Plugins Search

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical