Multiple unspecified vulnerabilities in Google V8 before 3.28.71.15, as used in Google Chrome before 38.0.2125.101, allow attackers to cause a denial of service or possibly have other impact via unknown vectors.

The remote Redhat Enterprise Linux 6 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - v8: IPC and v8 issue fixed in Google Chrome 38.0.2125.101 (CVE-2014-3188)

  - V8: integer overflow leading to buffer overflow in Zone::New (CVE-2016-1669)

  - Google V8, as used in Google Chrome before 38.0.2125.101, does not properly track JavaScript heap-memory     allocations as allocations of uninitialized memory and does not properly concatenate arrays of double-     precision floating-point numbers, which allows remote attackers to obtain sensitive information via     crafted JavaScript code, related to the PagedSpace::AllocateRaw and NewSpace::AllocateRaw functions in     heap/spaces-inl.h, the LargeObjectSpace::AllocateRaw function in heap/spaces.cc, and the     Runtime_ArrayConcat function in runtime.cc. (CVE-2014-3195)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

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

    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)

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.

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.

ID	Name	Product	Family	Severity
198942	RHEL 6 : v8 (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	high
78465	Ubuntu 14.04 LTS : Oxide vulnerabilities (USN-2345-1)	Nessus	Ubuntu Local Security Checks	high
78080	Google Chrome < 38.0.2125.101 Multiple Vulnerabilities	Nessus	Windows	critical

Detections

Analytics

CVE-2014-7967

high

Tenable Plugins

high

high

critical