Description
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.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 7 | chromium-browser | 28.0.1500.71-1~deb7u1 | DSA-2724-1 |
Advisories 1
- DSA-2724-1 chromium-browser - several Debian Security (DSA / DLA) · Mar 9, 2026
References
- https://code.google.com/p/chromium/issues/detail?id=244260
- http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=44b400c80726ee5d205a27730a0c846be656a071
- oval:org.mitre.oval:def:17033 vdb-entry signature
- DSA-2724 vendor-advisory
- http://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
- http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=f4f9f4948de5a59462e13ad712d7d9117238aeea