The version of Google Chrome installed on the remote host is a version prior to 28.0.1500.71 and is, therefore, affected by multiple vulnerabilities :

  - A vulnerability exists that exposes HTTP in SSL to a     man-in-the-middle attack. (CVE-2013-2853)

  - Block pop-unders in various scenarios. (CVE-2013-2867)

  - An error exists related to an incorrect sync of the     NPAPI extension component. (CVE-2013-2868)

  - An unspecified flaw exists due to a lack of entropy in     renderers. (CVE-2013-2872)

  - Use-after-free errors exist related to network sockets,     input handling, and resource loading. (CVE-2013-2870,     CVE-2013-2871, CVE-2013-2873)

  - A screen data leak error exists related to GL textures.
    (CVE-2013-2874)

  - An extension permission error exists related to     interstitials.  (CVE-2013-2876)

  - Multiple out-of-bounds errors exist related to JPEG2000,     SVG, text handling and XML parsing.  (CVE-2013-2869,     CVE-2013-2875, CVE-2013-2877, CVE-2013-2878)

  - An unspecified error exists when setting up sign-in and     sync. (CVE-2013-2879)

  - The vendor reports various, unspecified errors exist.
    (CVE-2013-2880)

The remote host is affected by the vulnerability described in GLSA-201309-16 (Chromium, V8: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Chromium and V8. Please       review the CVE identifiers and release notes referenced below for       details.
  Impact :

    A context-dependent attacker could entice a user to open a specially       crafted website or JavaScript program using Chromium or V8, possibly       resulting in the execution of arbitrary code with the privileges of the       process or a Denial of Service condition. Furthermore, a remote attacker       may be able to bypass security restrictions or have other, unspecified,       impact.
  Workaround :

    There is no known workaround at this time.

Several vulnerabilities have been discovered in the Chromium web browser.

  - CVE-2013-2853     The HTTPS implementation does not ensure that headers     are terminated by \r\n\r\n (carriage return, newline,     carriage return, newline).

  - CVE-2013-2867     Chrome does not properly prevent pop-under windows.

  - CVE-2013-2868     common/extensions/sync_helper.cc proceeds with sync     operations for NPAPI extensions without checking for a     certain plugin permission setting.

  - CVE-2013-2869     Denial of service (out-of-bounds read) via a crafted     JPEG2000 image.

  - CVE-2013-2870     Use-after-free vulnerability in network sockets.

  - CVE-2013-2871     Use-after-free vulnerability in input handling.

  - CVE-2013-2873     Use-after-free vulnerability in resource loading.

  - CVE-2013-2875     Out-of-bounds read in SVG file handling.

  - CVE-2013-2876     Chromium does not properly enforce restrictions on the     capture of screenshots by extensions, which could lead     to information disclosure from previous page visits.

  - CVE-2013-2877     Out-of-bounds read in XML file handling.

  - CVE-2013-2878     Out-of-bounds read in text handling.

  - CVE-2013-2879     The circumstances in which a renderer process can be     considered a trusted process for sign-in and subsequent     sync operations were not propertly checked.

  - CVE-2013-2880     The Chromium 28 development team found various issues     from internal fuzzing, audits, and other studies.

ID	Name	Product	Family	Published	Updated	Severity
67232	Google Chrome < 28.0.1500.71 Multiple Vulnerabilities	Nessus	Windows	7/10/2013	4/11/2022	high
70112	GLSA-201309-16 : Chromium, V8: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	9/25/2013	1/6/2021	critical
68970	Debian DSA-2724-1 : chromium-browser - several vulnerabilities	Nessus	Debian Local Security Checks	7/19/2013	1/11/2021	high

Detections

Analytics

Plugins Search

high

critical

high