Today we are publishing details of a vulnerability in the design of SSL version 3.0. This vulnerability allows the plaintext of secure connections to be calculated by a network attacker. I discovered this issue in collaboration with Thai Duong and Krzysztof Kotowicz (also Googlers).TLS_FALLBACK_SCSV . This is a mechanism that solves the problems caused by retrying failed connections and thus prevents attackers from inducing browsers to use SSL 3.0. It also prevents downgrades from TLS 1.2 to 1.1 or 1.0 and so may help prevent future attacks.Posted by Bodo Möller, Google Security Team [Updated Oct 15 to note that SSL 3.0 is nearly 18 years old, not nearly 15 years old.]
Follow
5 則留言 :
Does this apply to SSLv2 as well?
I can't wait to see POODLE take over the internet! Thank goodness we have heroes to save us from the evils of SSL 3.0 and such and such, etc.
Not sure how to enable TLS_FALLBACK_SCSV on apache or nginx.
To test I just disabled SSLv2 and SSLv3 on my personal https web site, so far so good all browsers (modern) traffic goes thru.
nvd still says it is under review. Is there a patch coming?
It's strange, but google.com is also vulnerable to POODLE attack:
https://www.ssllabs.com/ssltest/analyze.html?d=google.com&s=74.125.239.96&hideResults=on
張貼留言