Inappropriate use of www mismatch redirects in browser navigation in Google Chrome prior to 61.0.3163.79 for Mac, Windows, and Linux, and 61.0.3163.81 for Android, allowed a remote attacker to potentially downgrade HTTPS requests to HTTP via a crafted HTML page. In other words, Chrome could transmit cleartext even though the user had entered an https URL, because of a misdesigned workaround for cases where the domain name in a URL almost matches the domain name in an X.509 server certificate (but differs in the initial "www." substring).
Link | Tags |
---|---|
https://crbug.com/718676 | |
https://security.gentoo.org/glsa/201709-15 | vendor advisory |
https://access.redhat.com/errata/RHSA-2017:2676 | vendor advisory |
http://www.securitytracker.com/id/1039291 | vdb entry |
http://www.securityfocus.com/bid/100610 | vdb entry |
http://www.debian.org/security/2017/dsa-3985 | vendor advisory |
https://chromereleases.googleblog.com/2017/09/stable-channel-update-for-desktop.html |