Description
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.
References
- http://src.chromium.org/viewvc/chrome?view=rev&revision=11669
- http://code.google.com/p/chromium/issues/detail?id=7338
- http://research.microsoft.com/pubs/79323/pbp-final-with-update.pdf
- 35411 vdb-entry
- https://bugzilla.mozilla.org/show_bug.cgi?id=479880
- http://sites.google.com/a/chromium.org/dev/getting-involved/dev-channel/release-notes/releasenotes1015453
- http://code.google.com/p/chromium/issues/detail?id=8473
- http://src.chromium.org/viewvc/chrome/branches/release_154.next/src/net/http/http_transaction_winhttp.cc?r1=11621&r2=11669&pathrev=11669
- http://research.microsoft.com/apps/pubs/default.aspx?id=79323