CVE-2009-2060 json
src/net/http/http_transaction_winhttp.cc in Google Chrome before 1.0.154.53 uses the HTTP Host header to determine the context of a documen…
published 17y ago modified 5mo ago also EUVD-2009-2056
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
src/net/http/http_transaction_winhttp.cc in Google Chrome before 1.0.154.53 uses the HTTP Host header to determine the context of a document provided in a (1) 4xx or (2) 5xx CONNECT response from a proxy server, which allows man-in-the-middle attackers to execute arbitrary web script by modifying this CONNECT response, aka an "SSL tampering" attack.
Patch / fix
- google chrome 1.0.154.53
Is CVE-2009-2060 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.10% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-16).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
- Technology feeds
References
- src.chromium.org /viewvc/chrome?view=rev&revision=11669
- code.google.com /p/chromium/issues/detail?id=7338
- research.microsoft.com /pubs/79323/pbp-final-with-update.pdf
- bugzilla.mozilla.org /show_bug.cgi?id=479880
- sites.google.com /a/chromium.org/dev/getting-involved/dev-channel/release-notes/releasenotes1015453
-
exchange.xforce.ibmcloud.com
/vulnerabilities/51194
vdb-entry
- code.google.com /p/chromium/issues/detail?id=8473
- src.chromium.org /viewvc/chrome/branches/release_154.next/src/net/http/http_transaction_winhttp.cc?r1=11621&r2=11669&pathrev=11
- research.microsoft.com /apps/pubs/default.aspx?id=79323
Sources
- CVE List CVE-2009-2060
- NVD CVE-2009-2060
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.