openSUSE Security Update : v8 / chromium (openSUSE-2011-53)

The Chromium update to version 17.0.945 and v8 update to version 3.7.8.0 resolve serveral bugs as well as a security bug in v8 that could potentially be exploited to execute arbitrary code CVE-2011-3900. %NASLMINLEVEL 70300 C Tenable Network Security, Inc. The descriptive text and package checks ...

Gentoo Security Advisory GLSA 201111-05 (chromium v8)

The remote host is missing updates announced in advisory GLSA 201111-05. OpenVAS Vulnerability Test $ Description: Auto generated from Gentoo's XML based advisory Authors: Thomas Reinke Copyright: Copyright c 2012 E-Soft Inc. http://www.securityspace.com Text descriptions are largely excerpted fr...

Google Chrome < 15.0.874.121 V8 Out-of-bounds Write Unspecified Remote Memory Corruption

The version of Google Chrome installed on the remote host is earlier than 15.0.874.121 and is affected by an out-of-bounds memory write in the V8 JavaScript engine. Such an error can cause data corruption, application crashes or can potentially allow code execution. %NASLMINLEVEL 70300 C Tenable...

Google Chrome V8 Remote Code Execution Vulnerability (Mac OS X)

The host is installed with Google Chrome and is prone to remote code execution vulnerability. OpenVAS Vulnerability Test $Id: secpodgooglechromev8remotecodeexecvulnmacosx.nasl 7052 2017-09-04 11:50:51Z teissa $ Google Chrome V8 Remote Code Execution Vulnerability Mac OS X Authors: Rachana Shetty...

Google Chrome V8 Remote Code Execution Vulnerability - Windows

Google Chrome is prone to a remote code execution RCE vulnerability. SPDX-FileCopyrightText: 2011 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only ifdescription...

CVE-2011-3900

CVE-2011-3900 affects Google Chrome prior to 15.0.874.121, specifically a vulnerability in the V8 engine where an out-of-bounds write could lead to denial of service or potentially other impact. Public references in the connected documents confirm the Chrome/Chromium V8 context and the remediatio...