# CVE-2013-6628: Security feature bypass in n/a

> Remote attackers can bypass TLS trust relationships by exploiting certificate validation flaws during session renegotiation in Google Chrome.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-569f-wv52-cf97

## What is CVE-2013-6628?

CVE-2013-6628 is a medium-severity vulnerability in Google Chrome, published on 13 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

## Which versions are affected by CVE-2013-6628?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2013-6628?

Upgrade to a fixed version.

## Is CVE-2013-6628 being exploited?

There is no known exploitation of CVE-2013-6628 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6628 and fix it if it is affected.

What it is: CVE-2013-6628 is a medium-severity vulnerability in Google Chrome, published on 13 Nov 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-6628 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-6628/ (Markdown: https://insights.sbomify.com/CVE-2013-6628/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-6628
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-6628
- OSV: https://osv.dev/vulnerability/CVE-2013-6628

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-6628/
Summaries are generated and may contain mistakes; the official description above is the record.