CVE-2009-2071 json
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, wh…
published 17y ago modified 5mo ago also EUVD-2009-2067
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- google chrome 1.0.154.53
Is CVE-2009-2071 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.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-16).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-287 Improper Authentication
- Technology feeds
References
-
sites.google.com
/a/chromium.org/dev/getting-involved/dev-channel/release-notes/releasenotes1015453
patch
-
src.chromium.org
/viewvc/chrome/branches/release_154.next/src/net/http/http_transaction_winhttp.cc?r1=11621&r2=11669&pathrev=11
patch
- 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
-
securityfocus.com
/bid/35411
vdb-entry
- bugzilla.mozilla.org /show_bug.cgi?id=479880
- code.google.com /p/chromium/issues/detail?id=8473
- research.microsoft.com /apps/pubs/default.aspx?id=79323
Sources
- CVE List CVE-2009-2071
- NVD CVE-2009-2071
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.