cbcvebase.
CVE-2013-2853
published 2013-07-10

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…

PriorityP424medium6.8CVSS 2.0
AVNACMAuNCPIPAP
EPSS
1.15%
63.6th percentile
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.

Affected

63 ranges· showing 25
VendorProductVersion rangeFixed in
googlechrome<= 28.0.1500.70—
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
googlechrome——
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.