Issue metadata
Sign in to add a comment
|
Security: MitM allows reading HTTPS data without SSL-Offloading through WPAD. Extremely Severe
Reported by
bas.ve...@gmail.com,
May 26 2016
|
||||||||||||||||||||||
Issue descriptionPlease handle this report with upmost care, Chrome is not the only product vulnerable for this behavior. Coordinated disclosure is required. VULNERABILITY DETAILS WPAD (autoconfiguration) and proxy.pac behavior allows an attacker on the same network to intercept all full paths & GET Data of every HTTPS request made through Chrome (and other software). The root-issue seems to be that for HTTPS requests, the full url including the path & parameters is passed to FindProxyForURL() which can be exfiltrated by using forced DNS resolutions using dnsResolve(). The POC automaticly encodes the URL's to a format transferable over DNS. VERSION Chrome Version: 51.0.2704.63 m , most likely all versions with support for WPAD. Operating System: Various, including windows 8, 10 REPRODUCTION CASE Attached are a wpad.dat and proxy.pac provisioning file. Both will work either staticly configured or served on http://wpad/wpad.dat or configured via DHCP. For easy reproduction, you can also run chrome.exe --proxy-pac-url="file:///D:\proxy.pac" A video demonstrating the issue can be found here: https://www.youtube.com/watch?v=_jh1A0tA4PI The POC shows how a victious password reset link at 'https://www.google.com/passwordresettoken=pocexample' could be intercepted. I came accross this issue when thinkering with WPAD after seeing https://www.us-cert.gov/ncas/alerts/TA16-144A this vulnerability, and realising that wasn't the scariest part about it all. Please note that combined with ^ that issue, this could remotely breach HTTPS on carrier/ISP level. I have not yet found how many products and operating systems are vulnerable, but this seems to be a VERY widespread issue. I'd like to ask your help to coordinate this disclosure to other parties (e.g other browser vendors). Feel free to contact me for more info or help with reproducing the issue. Cheers!
,
May 26 2016
Is this the same as Issue 593759 (already fixed and public)?
,
May 26 2016
https://bugs.chromium.org/p/chromium/issues/detail?id=593759 is not public atm, can you grant me access or send me the info in some other way?
,
May 26 2016
eroman: Can you please triage? As lgarron pointed, issue 593759 looks similar.
,
May 26 2016
Correct, this is a duplicate of issue 593759 . The latest Canary build of Chromium has a fix: https://chromium.googlesource.com/chromium/src/+/81357b39c643fc746517fd6ce5cb2076b7ddc3f4
,
May 26 2016
Yes, this is the same as issue 593759 .
,
Sep 2 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 1 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 2 2016
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 2 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bas.ve...@gmail.com
, May 26 2016