Google V8, as used in Google Chrome before 2.0.172.43, allows remote attackers to bypass intended restrictions on reading memory, and possibly obtain sensitive information or execute arbitrary code in the Chrome sandbox, via crafted JavaScript.

The version of Google Chrome installed on the remote host is earlier than 2.0.172.43.  Such versions have a flaw in the V8 Javascript engine which could potentially allow specially-crafted Javascript on a eb page to read unauthorize memory, bypassing security checks. An attacker could exploit this to run arbitrary code within the Chrome sand-box.

The version of Google Chrome installed on the remote host is earlier than 2.0.172.43.  Such versions are reportedly affected by multiple issues :

  - A flaw in the V8 JavaScript engine might allow a     specially crafted JavaScript page to access     unauthorized data in memory or to execute arbitrary code     within the Google Chrome sandbox. (CVE-2009-2935)

  - The browser can connect to SSL-enabled sites whose     certificates use weak hash algorithms, such as MD2 and     MD4. An attacker may be able exploit this issue to     forge certificates and spoof an invalid website as a     valid HTTPS site. (Issue #18725)

  - A stack consumption vulnerability in libxml2 library     could be exploited to crash the Google Chrome tab process     or execute arbitrary code with in Google Chrome sandbox.
    (CVE-2009-2414)

  - Multiple use-after-free vulnerabilities in libxml2     library could be exploited to crash the Google Chrome     tab process or execute arbitrary code with in Google     Chrome sandbox. (CVE-2009-2416)

ID	Name	Product	Family	Severity
800939	Google Chrome < 2.0.172.43 Remote Code Execution	Log Correlation Engine	Web Clients	high
5141	Google Chrome < 2.0.172.43 RCE	Nessus Network Monitor	Web Clients	medium
40778	Google Chrome < 2.0.172.43 Multiple Vulnerabilities	Nessus	Windows	high

Detections

Analytics

CVE-2009-2935

high

Tenable Plugins

high

medium

high