CVE-2013-2853
First published: Wed Jul 10 2013(Updated: )
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.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <=28.0.1500.70 | |
| Google Chrome (Trace Event) | =28.0.1500.0 | |
| Google Chrome (Trace Event) | =28.0.1500.2 | |
| Google Chrome (Trace Event) | =28.0.1500.3 | |
| Google Chrome (Trace Event) | =28.0.1500.4 | |
| Google Chrome (Trace Event) | =28.0.1500.5 | |
| Google Chrome (Trace Event) | =28.0.1500.6 | |
| Google Chrome (Trace Event) | =28.0.1500.8 | |
| Google Chrome (Trace Event) | =28.0.1500.9 | |
| Google Chrome (Trace Event) | =28.0.1500.10 | |
| Google Chrome (Trace Event) | =28.0.1500.11 | |
| Google Chrome (Trace Event) | =28.0.1500.12 | |
| Google Chrome (Trace Event) | =28.0.1500.13 | |
| Google Chrome (Trace Event) | =28.0.1500.14 | |
| Google Chrome (Trace Event) | =28.0.1500.15 | |
| Google Chrome (Trace Event) | =28.0.1500.16 | |
| Google Chrome (Trace Event) | =28.0.1500.17 | |
| Google Chrome (Trace Event) | =28.0.1500.18 | |
| Google Chrome (Trace Event) | =28.0.1500.19 | |
| Google Chrome (Trace Event) | =28.0.1500.20 | |
| Google Chrome (Trace Event) | =28.0.1500.21 | |
| Google Chrome (Trace Event) | =28.0.1500.22 | |
| Google Chrome (Trace Event) | =28.0.1500.23 | |
| Google Chrome (Trace Event) | =28.0.1500.24 | |
| Google Chrome (Trace Event) | =28.0.1500.25 | |
| Google Chrome (Trace Event) | =28.0.1500.26 | |
| Google Chrome (Trace Event) | =28.0.1500.27 | |
| Google Chrome (Trace Event) | =28.0.1500.28 | |
| Google Chrome (Trace Event) | =28.0.1500.29 | |
| Google Chrome (Trace Event) | =28.0.1500.31 | |
| Google Chrome (Trace Event) | =28.0.1500.32 | |
| Google Chrome (Trace Event) | =28.0.1500.33 | |
| Google Chrome (Trace Event) | =28.0.1500.34 | |
| Google Chrome (Trace Event) | =28.0.1500.35 | |
| Google Chrome (Trace Event) | =28.0.1500.36 | |
| Google Chrome (Trace Event) | =28.0.1500.37 | |
| Google Chrome (Trace Event) | =28.0.1500.38 | |
| Google Chrome (Trace Event) | =28.0.1500.39 | |
| Google Chrome (Trace Event) | =28.0.1500.40 | |
| Google Chrome (Trace Event) | =28.0.1500.41 | |
| Google Chrome (Trace Event) | =28.0.1500.42 | |
| Google Chrome (Trace Event) | =28.0.1500.43 | |
| Google Chrome (Trace Event) | =28.0.1500.44 | |
| Google Chrome (Trace Event) | =28.0.1500.45 | |
| Google Chrome (Trace Event) | =28.0.1500.46 | |
| Google Chrome (Trace Event) | =28.0.1500.47 | |
| Google Chrome (Trace Event) | =28.0.1500.48 | |
| Google Chrome (Trace Event) | =28.0.1500.49 | |
| Google Chrome (Trace Event) | =28.0.1500.50 | |
| Google Chrome (Trace Event) | =28.0.1500.51 | |
| Google Chrome (Trace Event) | =28.0.1500.52 | |
| Google Chrome (Trace Event) | =28.0.1500.53 | |
| Google Chrome (Trace Event) | =28.0.1500.54 | |
| Google Chrome (Trace Event) | =28.0.1500.56 | |
| Google Chrome (Trace Event) | =28.0.1500.58 | |
| Google Chrome (Trace Event) | =28.0.1500.59 | |
| Google Chrome (Trace Event) | =28.0.1500.60 | |
| Google Chrome (Trace Event) | =28.0.1500.61 | |
| Google Chrome (Trace Event) | =28.0.1500.62 | |
| Google Chrome (Trace Event) | =28.0.1500.63 | |
| Google Chrome (Trace Event) | =28.0.1500.64 | |
| Google Chrome (Trace Event) | =28.0.1500.66 | |
| Google Chrome (Trace Event) | =28.0.1500.68 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://git.chromium.org/gitweb/?p=chromium/chromium.git;a=commit;h=44b400c80726ee5d205a27730a0c846be656a071
- http://git.chromium.org/gitweb/?p=chromium/chromium.git;a=commit;h=f4f9f4948de5a59462e13ad712d7d9117238aeea
- http://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
- http://www.debian.org/security/2013/dsa-2724
- https://code.google.com/p/chromium/issues/detail?id=244260
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A17033
Frequently Asked Questions
What is the severity of CVE-2013-2853?
CVE-2013-2853 is categorized as a high severity vulnerability due to its potential for man-in-the-middle attacks.
How do I fix CVE-2013-2853?
To mitigate CVE-2013-2853, upgrade to Google Chrome version 28.0.1500.71 or later.
What types of attacks can exploit CVE-2013-2853?
CVE-2013-2853 can be exploited by man-in-the-middle attackers through header truncation vectors.
Which versions of Google Chrome are affected by CVE-2013-2853?
All versions of Google Chrome prior to 28.0.1500.71 are affected by CVE-2013-2853.
What does CVE-2013-2853 affect in Google Chrome?
CVE-2013-2853 affects the HTTPS implementation in Google Chrome, allowing for potential security vulnerabilities.
- agent/references
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- agent/type
- agent/author
- agent/severity
- agent/tags
- agent/description
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/google chrome (trace event)
- version/google chrome (trace event)/28.0.1500.70
- version/google chrome (trace event)/28.0.1500.0
- version/google chrome (trace event)/28.0.1500.2
- version/google chrome (trace event)/28.0.1500.3
- version/google chrome (trace event)/28.0.1500.4
- version/google chrome (trace event)/28.0.1500.5
- version/google chrome (trace event)/28.0.1500.6
- version/google chrome (trace event)/28.0.1500.8
- version/google chrome (trace event)/28.0.1500.9
- version/google chrome (trace event)/28.0.1500.10
- version/google chrome (trace event)/28.0.1500.11
- version/google chrome (trace event)/28.0.1500.12
- version/google chrome (trace event)/28.0.1500.13
- version/google chrome (trace event)/28.0.1500.14
- version/google chrome (trace event)/28.0.1500.15
- version/google chrome (trace event)/28.0.1500.16
- version/google chrome (trace event)/28.0.1500.17
- version/google chrome (trace event)/28.0.1500.18
- version/google chrome (trace event)/28.0.1500.19
- version/google chrome (trace event)/28.0.1500.20
- version/google chrome (trace event)/28.0.1500.21
- version/google chrome (trace event)/28.0.1500.22
- version/google chrome (trace event)/28.0.1500.23
- version/google chrome (trace event)/28.0.1500.24
- version/google chrome (trace event)/28.0.1500.25
- version/google chrome (trace event)/28.0.1500.26
- version/google chrome (trace event)/28.0.1500.27
- version/google chrome (trace event)/28.0.1500.28
- version/google chrome (trace event)/28.0.1500.29
- version/google chrome (trace event)/28.0.1500.31
- version/google chrome (trace event)/28.0.1500.32
- version/google chrome (trace event)/28.0.1500.33
- version/google chrome (trace event)/28.0.1500.34
- version/google chrome (trace event)/28.0.1500.35
- version/google chrome (trace event)/28.0.1500.36
- version/google chrome (trace event)/28.0.1500.37
- version/google chrome (trace event)/28.0.1500.38
- version/google chrome (trace event)/28.0.1500.39
- version/google chrome (trace event)/28.0.1500.40
- version/google chrome (trace event)/28.0.1500.41
- version/google chrome (trace event)/28.0.1500.42
- version/google chrome (trace event)/28.0.1500.43
- version/google chrome (trace event)/28.0.1500.44
- version/google chrome (trace event)/28.0.1500.45
- version/google chrome (trace event)/28.0.1500.46
- version/google chrome (trace event)/28.0.1500.47
- version/google chrome (trace event)/28.0.1500.48
- version/google chrome (trace event)/28.0.1500.49
- version/google chrome (trace event)/28.0.1500.50
- version/google chrome (trace event)/28.0.1500.51
- version/google chrome (trace event)/28.0.1500.52
- version/google chrome (trace event)/28.0.1500.53
- version/google chrome (trace event)/28.0.1500.54
- version/google chrome (trace event)/28.0.1500.56
- version/google chrome (trace event)/28.0.1500.58
- version/google chrome (trace event)/28.0.1500.59
- version/google chrome (trace event)/28.0.1500.60
- version/google chrome (trace event)/28.0.1500.61
- version/google chrome (trace event)/28.0.1500.62
- version/google chrome (trace event)/28.0.1500.63
- version/google chrome (trace event)/28.0.1500.64
- version/google chrome (trace event)/28.0.1500.66
- version/google chrome (trace event)/28.0.1500.68