# CVE-2013-6166: Cross-site request forgery in n/a

> Remote attackers can force persistent logout via CSRF by exploiting Chrome's lack of cookie character validation, requiring user interaction.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** No
- **Published:** 15 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c3rj-c9pq-rmgx

## What is CVE-2013-6166?

CVE-2013-6166 is a medium-severity vulnerability in Google Chrome, published on 15 Feb 2014. 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

Google Chrome before 29 sends HTTP Cookie headers without first validating that they have the required character-set restrictions, which allows remote attackers to conduct the equivalent of a persistent Logout CSRF attack via a crafted parameter that forces a web application to set a malformed cookie within an HTTP response.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Google Chrome.

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

No fix has been published for CVE-2013-6166 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-6166 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6166 exists.

Public exploit code:

- Google Chrome - Cookie Verification Denial of Service (exploitdb)

## 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-6166 and fix it if it is affected.

What it is: CVE-2013-6166 is a medium-severity vulnerability in Google Chrome, published on 15 Feb 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6166 exists.

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-6166/ (Markdown: https://insights.sbomify.com/CVE-2013-6166/index.md)
```

## Sources

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

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