net/socket/ssl_client_socket_nss.cc in the TLS implementation in Google Chrome before 31.0.1650.48 does not ensure that a server's X.509 certificate is the same during renegotiation as it was before renegotiation, which might allow remote web servers to interfere with trust relationships by renegotiating a session.
https://src.chromium.org/viewvc/chrome?revision=229611&view=revision
https://secure-resumption.com/
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19108
https://code.google.com/p/chromium/issues/detail?id=306959
http://www.debian.org/security/2013/dsa-2799
http://lists.opensuse.org/opensuse-updates/2014-01/msg00042.html
http://lists.opensuse.org/opensuse-security-announce/2013-12/msg00002.html
http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00026.html
http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00025.html
http://googlechromereleases.blogspot.com/2013/11/stable-channel-update.html