CVE-2013-6628
Last modified
CVE-2013-6628 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.02% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | <= 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
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-6628?
How severe is CVE-2013-6628?
How do I fix CVE-2013-6628?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-6622Use-after-free vulnerability in the HTMLMediaElement::didMov…
- CVE-2013-6623The SVG implementation in Blink, as used in Google Chrome be…
- CVE-2013-6624Use-after-free vulnerability in Google Chrome before 31.0.16…
- CVE-2013-6625Use-after-free vulnerability in core/dom/ContainerNode.cpp i…
- CVE-2013-6626The WebContentsImpl::AttachInterstitialPage function in cont…
- CVE-2013-6627net/http/http_stream_parser.cc in Google Chrome before 31.0.…
- CVE-2013-6629The get_sos function in jdmarker.c in (1) libjpeg 6b and (2)…
- CVE-2013-6630The get_dht function in jdmarker.c in libjpeg-turbo through …
- CVE-2013-6631Use-after-free vulnerability in the Channel::SendRTCPPacket …
- CVE-2013-6632Integer overflow in Google Chrome before 31.0.1650.57 allows…
- CVE-2013-6634The OneClickSigninHelper::ShowInfoBarIfPossible function in …
- CVE-2013-6635Use-after-free vulnerability in the editing implementation i…
Are you affected by CVE-2013-6628?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
