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.

Score

CVSS 2.0 6.8 Medium

Status

Modified - chrome-cve-admin@google.com

Published

2013-07-10

Last modified

2024-08-06

Affected products

• Chrome (Google)

References

• http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=44b400c80726ee5d205a27730a0c846be656a071
• http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=f4f9f4948de5a59462e13ad712d7d9117238aeea
• http://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
• http://www.debian.org/security/2013/dsa-2724
• https://code.google.com/p/chromium/issues/detail?id=244260
• https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A17033