CVE-2013-2853

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 (12)

• chrome-cve-admin@googlehttp://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=44b400c80726ee5d205a27730a0c846be656a071
• chrome-cve-admin@googlehttp://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=f4f9f4948de5a59462e13ad712d7d9117238aeea
• chrome-cve-admin@googlehttp://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
• chrome-cve-admin@googlehttp://www.debian.org/security/2013/dsa-2724
• chrome-cve-admin@googlehttps://code.google.com/p/chromium/issues/detail?id=244260
• chrome-cve-admin@googlehttps://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A17033
• af854a3a-2127-422b-91ae-364da2661108http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=44b400c80726ee5d205a27730a0c846be656a071
• af854a3a-2127-422b-91ae-364da2661108http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=f4f9f4948de5a59462e13ad712d7d9117238aeea
• af854a3a-2127-422b-91ae-364da2661108http://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
• af854a3a-2127-422b-91ae-364da2661108http://www.debian.org/security/2013/dsa-2724
• af854a3a-2127-422b-91ae-364da2661108https://code.google.com/p/chromium/issues/detail?id=244260
• af854a3a-2127-422b-91ae-364da2661108https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A17033