Strix
26.1K

CVE-2013-2853

UnknownEPSS 1.15%

Last modified

CVE-2013-2853 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.15% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
1.15%

62.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
GoogleChrome<= 28.0.1500.70
GoogleChrome28.0.1500.0
GoogleChrome28.0.1500.2
GoogleChrome28.0.1500.3
GoogleChrome28.0.1500.4
GoogleChrome28.0.1500.5
GoogleChrome28.0.1500.6
GoogleChrome28.0.1500.8
GoogleChrome28.0.1500.9
GoogleChrome28.0.1500.10
GoogleChrome28.0.1500.11
GoogleChrome28.0.1500.12
GoogleChrome28.0.1500.13
GoogleChrome28.0.1500.14
GoogleChrome28.0.1500.15
GoogleChrome28.0.1500.16
GoogleChrome28.0.1500.17
GoogleChrome28.0.1500.18
GoogleChrome28.0.1500.19
GoogleChrome28.0.1500.20
GoogleChrome28.0.1500.21
GoogleChrome28.0.1500.22
GoogleChrome28.0.1500.23
GoogleChrome28.0.1500.24
GoogleChrome28.0.1500.25
GoogleChrome28.0.1500.26
GoogleChrome28.0.1500.27
GoogleChrome28.0.1500.28
GoogleChrome28.0.1500.29
GoogleChrome28.0.1500.31
GoogleChrome28.0.1500.32
GoogleChrome28.0.1500.33
GoogleChrome28.0.1500.34
GoogleChrome28.0.1500.35
GoogleChrome28.0.1500.36
GoogleChrome28.0.1500.37
GoogleChrome28.0.1500.38
GoogleChrome28.0.1500.39
GoogleChrome28.0.1500.40
GoogleChrome28.0.1500.41
GoogleChrome28.0.1500.42
GoogleChrome28.0.1500.43
GoogleChrome28.0.1500.44
GoogleChrome28.0.1500.45
GoogleChrome28.0.1500.46
GoogleChrome28.0.1500.47
GoogleChrome28.0.1500.48
GoogleChrome28.0.1500.49
GoogleChrome28.0.1500.50
GoogleChrome28.0.1500.51

Showing 50 of 63 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.
How severe is CVE-2013-2853?
Severity scoring for CVE-2013-2853 is pending analysis. The EPSS model estimates a 1.15% probability of exploitation in the next 30 days.
How do I fix CVE-2013-2853?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2013-2853?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST