First published: Thu Feb 18 2010(Updated: )
Google Chrome before 4.0.249.78 sends an https URL in the Referer header of an http request in certain circumstances involving https to http redirection, which allows remote HTTP servers to obtain potentially sensitive information via standard HTTP logging.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Google Chrome | <=4.0.249.0 | |
Google Chrome | =0.2.149.27 | |
Google Chrome | =0.2.149.29 | |
Google Chrome | =0.2.149.30 | |
Google Chrome | =0.2.152.1 | |
Google Chrome | =0.2.153.1 | |
Google Chrome | =0.3.154.0 | |
Google Chrome | =0.3.154.3 | |
Google Chrome | =0.4.154.18 | |
Google Chrome | =0.4.154.22 | |
Google Chrome | =0.4.154.31 | |
Google Chrome | =0.4.154.33 | |
Google Chrome | =1.0.154.36 | |
Google Chrome | =1.0.154.39 | |
Google Chrome | =1.0.154.42 | |
Google Chrome | =1.0.154.43 | |
Google Chrome | =1.0.154.46 | |
Google Chrome | =1.0.154.48 | |
Google Chrome | =1.0.154.52 | |
Google Chrome | =1.0.154.53 | |
Google Chrome | =1.0.154.59 | |
Google Chrome | =1.0.154.65 | |
Google Chrome | =2.0.156.1 | |
Google Chrome | =2.0.157.0 | |
Google Chrome | =2.0.157.2 | |
Google Chrome | =2.0.158.0 | |
Google Chrome | =2.0.159.0 | |
Google Chrome | =2.0.169.0 | |
Google Chrome | =2.0.169.1 | |
Google Chrome | =2.0.170.0 | |
Google Chrome | =2.0.172 | |
Google Chrome | =2.0.172.2 | |
Google Chrome | =2.0.172.8 | |
Google Chrome | =2.0.172.27 | |
Google Chrome | =2.0.172.28 | |
Google Chrome | =2.0.172.30 | |
Google Chrome | =2.0.172.31 | |
Google Chrome | =2.0.172.33 | |
Google Chrome | =2.0.172.37 | |
Google Chrome | =2.0.172.38 | |
Google Chrome | =3.0.182.2 | |
Google Chrome | =3.0.190.2 | |
Google Chrome | =3.0.193.2-beta | |
Google Chrome | =3.0.195.21 | |
Google Chrome | =3.0.195.24 | |
Google Chrome | =3.0.195.32 | |
Google Chrome | =3.0.195.33 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-0660 is classified as a moderate severity vulnerability due to potential exposure of sensitive information.
To fix CVE-2010-0660, users should update Google Chrome to version 4.0.249.78 or later.
CVE-2010-0660 affects various versions of Google Chrome prior to 4.0.249.78, including 0.2.x, 1.x, 2.x, and 3.x series.
CVE-2010-0660 may allow remote HTTP servers to obtain potentially sensitive information from the Referer header of a request.
There is no specific workaround for CVE-2010-0660; the recommended action is to update to a secure version of Google Chrome.