Google Chrome before 1.0.154.53 displays a cached certificate for a (1) 4xx or (2) 5xx CONNECT response page returned by a proxy server, which allows man-in-the-middle attackers to spoof an arbitrary https site by letting a browser obtain a valid certificate from this site during one request, and then sending the browser a crafted 502 response page upon a subsequent request.

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

  - The browser uses the HTTP Host header to determine the     context of a 4xx/5xx CONNECT response from a proxy     server. This could allow a man-in-the-middle attacker     to execute arbitrary script code in the context of a     legitimate server, circumventing the browser's same-     origin policy.

  - The browser displays a cached certificate for 4xx/5xx     CONNECT response pages from a proxy server.  A man-in-     the-middle attacker could exploit this by displaying a     spoofed web page with the valid certificate of a     legitimate website.

The version of Safari installed on the remote Windows host is earlier than 3.2.2.  Such versions reportedly have multiple vulnerabilities : 

  - Multiple input validation issues in their handling of 'feed: ' URLs, which could be abused to execute arbitrary JavaScript code in the local security zone. (CVE-2009-0137)

  - A cached certificate is not required before displaying a lock icon for a HTTPS web site. This allows a man-in-the-middle attacker to present the user with spoofed web pages over HTTPS that appear to be from a legitimate source. (CVE-2009-2072)

  - The browser processes a 3xxx HTTP CONNECT before a successful SSL handshake, which could allow a man-in-the-midddle attacker to execute arbitrary script code in the context of a HTTPS site. (CVE-2009-2062)

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

  - The browser uses the HTTP Host header to determine the context of a 4xx/5xx CONNECT response from a proxy server. This could allow a man-in-the-middle attacker to execute arbitrary script code in the context of a legitimate server. (CVE-2009-2060)

  - The browser displays a cached certificate for 4xx/5xx CONNECT response pages from a proxy server. A man-in-the-middle attacker could exploit this by displaying a spoofed web page with the valid certificate of a legitimate website.

ID	Name	Product	Family	Severity
39449	Google Chrome < 1.0.154.53 Multiple Vulnerabilities	Nessus	Windows	medium
4932	Safari < 3.2.2 Multiple Vulnerabilities	Nessus Network Monitor	Web Clients	high
801011	Safari < 3.2.2 Multiple Vulnerabilities	Log Correlation Engine	Web Clients	high
800933	Google Chrome < 1.0.154.53 Multiple Vulnerabilities	Log Correlation Engine	Web Clients	medium

Detections

Analytics

CVE-2009-2071

medium

Tenable Plugins

medium

high

high

medium