The HTTPS implementation in Google Chrome before 28.0.1500.71 does not ensure that headers are terminated by \r\n\r\n (carriage return, newline, carriage return, newline), which allows man-in-the-middle attackers to have an unspecified impact via vectors that trigger header truncation.
References
Configurations
Configuration 1 (hide)
|
Information
Published : 2013-07-10 03:55
Updated : 2017-09-18 18:36
NVD link : CVE-2013-2853
Mitre link : CVE-2013-2853
JSON object : View
CWE
Products Affected
- chrome