Google Chrome before 29 sends HTTP Cookie headers without first validating that they have the required character-set restrictions, which al…

published 2014-02-15 12 y ago modified 2026-06-17 4 mo ago also EUVD-2013-5995

cvss: 6.8; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.9%; EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits: 1; Exploit-DB

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.

Timeline

2013-04-04 First public exploit (EDB-38420)
2014-02-15 Published

Exploit prediction

1.86% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

EDB-38420 Google Chrome - Cookie Verification Denial of Service dos, 2013-04-04

CVSS scores

assigned by	version	score	vector
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

CWE-352 Cross-Site Request Forgery

Technology feeds

Google Chrome rss critical rss

References

seclists.org /oss-sec/2013/q4/121
mailing-list
seclists.org /oss-sec/2013/q4/117
mailing-list
openwall.com /lists/oss-security/2013/04/03/10
mailing-list
redmine.lighttpd.net /issues/2188
code.google.com /p/chromium/issues/detail?id=238041

Sources

CVE List CVE-2013-6166
NVD CVE-2013-6166

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary