CVE-2013-6628
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| chrome | {"endIncluding":"31.0.1650.47"} | | |
| chrome | 31.0.1650.0 | | |
| chrome | 31.0.1650.2 | | |
| chrome | 31.0.1650.3 | | |
| chrome | 31.0.1650.4 | | |
| chrome | 31.0.1650.5 | | |
| chrome | 31.0.1650.6 | | |
| chrome | 31.0.1650.7 | | |
| chrome | 31.0.1650.8 | | |
| chrome | 31.0.1650.9 | | |
| chrome | 31.0.1650.10 | | |
| chrome | 31.0.1650.11 | | |
| chrome | 31.0.1650.12 | | |
| chrome | 31.0.1650.13 | | |
| chrome | 31.0.1650.14 | | |
| chrome | 31.0.1650.15 | | |
| chrome | 31.0.1650.16 | | |
| chrome | 31.0.1650.17 | | |
| chrome | 31.0.1650.18 | | |
| chrome | 31.0.1650.19 | | |
| chrome | 31.0.1650.20 | | |
| chrome | 31.0.1650.22 | | |
| chrome | 31.0.1650.23 | | |
| chrome | 31.0.1650.25 | | |
| chrome | 31.0.1650.26 | | |
| chrome | 31.0.1650.27 | | |
| chrome | 31.0.1650.28 | | |
| chrome | 31.0.1650.29 | | |
| chrome | 31.0.1650.30 | | |
| chrome | 31.0.1650.31 | | |
| chrome | 31.0.1650.32 | | |
| chrome | 31.0.1650.33 | | |
| chrome | 31.0.1650.34 | | |
| chrome | 31.0.1650.35 | | |
| chrome | 31.0.1650.36 | | |
| chrome | 31.0.1650.37 | | |
| chrome | 31.0.1650.38 | | |
| chrome | 31.0.1650.39 | | |
| chrome | 31.0.1650.41 | | |
| chrome | 31.0.1650.42 | | |
| chrome | 31.0.1650.43 | | |
| chrome | 31.0.1650.44 | | |
| chrome | 31.0.1650.45 | | |
| chrome | 31.0.1650.46 | |
References
- http://googlechromereleases.blogspot.com/2013/11/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00025.html
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00026.html
- http://lists.opensuse.org/opensuse-security-announce/2013-12/msg00002.html
- http://lists.opensuse.org/opensuse-updates/2014-01/msg00042.html
- http://www.debian.org/security/2013/dsa-2799
- https://code.google.com/p/chromium/issues/detail?id=306959
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19108
- https://secure-resumption.com/
- https://src.chromium.org/viewvc/chrome?revision=229611&view=revision
- http://googlechromereleases.blogspot.com/2013/11/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00025.html
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00026.html
- http://lists.opensuse.org/opensuse-security-announce/2013-12/msg00002.html
- http://lists.opensuse.org/opensuse-updates/2014-01/msg00042.html
- http://www.debian.org/security/2013/dsa-2799
- https://code.google.com/p/chromium/issues/detail?id=306959
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19108
- https://secure-resumption.com/
- https://src.chromium.org/viewvc/chrome?revision=229611&view=revision
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.