Vulnerability in Google Chrome
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.
Published · last modified .
CVSS v2 metric
CVSS v2 base score 6.8 (Medium). Vector: AV:N/AC:M/Au:N/C:P/I:P/A:P. This CVE predates CVSS v3 and has no v3 score from NVD.
EPSS exploit prediction
EPSS: 0.011 (64.9th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 65th percentile — 64.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.011 · newest: 0.011 · change: 0.000
Affected products
- Google Chrome — versions 28.0.1500.0, 28.0.1500.2, 28.0.1500.3
References
- code.google.com/p/chromium/issues/detail
- git.chromium.org/gitweb/
- oval.cisecurity.org/repository/search/definition/oval:org.mitre.oval:def:17033 (signature, vdb-entry)
- www.debian.org/security/2013/dsa-2724 (vendor-advisory)
- googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
- git.chromium.org/gitweb/