CVE-2013-2853
Published: 10 July 2013
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.
Priority
Status
Package | Release | Status |
---|---|---|
chromium-browser Launchpad, Ubuntu, Debian |
lucid |
Ignored
(end of life)
|
precise |
Released
(28.0.1500.71-0ubuntu1.12.04.1)
|
|
quantal |
Released
(28.0.1500.71-0ubuntu1.12.10.1)
|
|
raring |
Released
(28.0.1500.71-0ubuntu1.13.04.1)
|
|
upstream |
Released
(28.0.1500.71)
|
References
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-2853
- https://code.google.com/p/chromium/issues/detail?id=244260
- http://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
- http://git.chromium.org/gitweb/?p=chromium/chromium.git;a=commit;h=f4f9f4948de5a59462e13ad712d7d9117238aeea
- http://git.chromium.org/gitweb/?p=chromium/chromium.git;a=commit;h=44b400c80726ee5d205a27730a0c846be656a071
- NVD
- Launchpad
- Debian