CVE-2010-0660 json
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 htt…
published 2010-02-18 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-0691
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- google chrome 4.0.249.78
Exploit prediction
0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
googlechromereleases.blogspot.com
/2010/01/stable-channel-update_25.html
patch
-
sites.google.com
/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14247
vdb-entry, signature
-
securitytracker.com
/id?1023506
vdb-entry
- code.google.com /p/chromium/issues/detail?id=29920
Sources
- CVE List CVE-2010-0660
- NVD CVE-2010-0660
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Consolidate version ranges.