CVE-2013-2853
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
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | <= 28.0.1500.70 | |
| Chrome | 28.0.1500.0 | |
| Chrome | 28.0.1500.2 | |
| Chrome | 28.0.1500.3 | |
| Chrome | 28.0.1500.4 | |
| Chrome | 28.0.1500.5 | |
| Chrome | 28.0.1500.6 | |
| Chrome | 28.0.1500.8 | |
| Chrome | 28.0.1500.9 | |
| Chrome | 28.0.1500.10 | |
| Chrome | 28.0.1500.11 | |
| Chrome | 28.0.1500.12 | |
| Chrome | 28.0.1500.13 | |
| Chrome | 28.0.1500.14 | |
| Chrome | 28.0.1500.15 | |
| Chrome | 28.0.1500.16 | |
| Chrome | 28.0.1500.17 | |
| Chrome | 28.0.1500.18 | |
| Chrome | 28.0.1500.19 | |
| Chrome | 28.0.1500.20 | |
| Chrome | 28.0.1500.21 | |
| Chrome | 28.0.1500.22 | |
| Chrome | 28.0.1500.23 | |
| Chrome | 28.0.1500.24 | |
| Chrome | 28.0.1500.25 | |
| Chrome | 28.0.1500.26 | |
| Chrome | 28.0.1500.27 | |
| Chrome | 28.0.1500.28 | |
| Chrome | 28.0.1500.29 | |
| Chrome | 28.0.1500.31 | |
| Chrome | 28.0.1500.32 | |
| Chrome | 28.0.1500.33 | |
| Chrome | 28.0.1500.34 | |
| Chrome | 28.0.1500.35 | |
| Chrome | 28.0.1500.36 | |
| Chrome | 28.0.1500.37 | |
| Chrome | 28.0.1500.38 | |
| Chrome | 28.0.1500.39 | |
| Chrome | 28.0.1500.40 | |
| Chrome | 28.0.1500.41 | |
| Chrome | 28.0.1500.42 | |
| Chrome | 28.0.1500.43 | |
| Chrome | 28.0.1500.44 | |
| Chrome | 28.0.1500.45 | |
| Chrome | 28.0.1500.46 | |
| Chrome | 28.0.1500.47 | |
| Chrome | 28.0.1500.48 | |
| Chrome | 28.0.1500.49 | |
| Chrome | 28.0.1500.50 | |
| Chrome | 28.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?
How severe is CVE-2013-2853?
How do I fix CVE-2013-2853?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-2847Race condition in the workers implementation in Google Chrom…
- CVE-2013-2848The XSS Auditor in Google Chrome before 27.0.1453.93 might a…
- CVE-2013-2849Multiple cross-site scripting (XSS) vulnerabilities in Googl…
- CVE-2013-2850Heap-based buffer overflow in the iscsi_add_notunderstood_re…
- CVE-2013-2851Format string vulnerability in the register_disk function in…
- CVE-2013-2852Format string vulnerability in the b43_request_firmware func…
- CVE-2013-2854Google Chrome before 27.0.1453.110 on Windows provides an in…
- CVE-2013-2855The Developer Tools API in Google Chrome before 27.0.1453.11…
- CVE-2013-2856Use-after-free vulnerability in Google Chrome before 27.0.14…
- CVE-2013-2857Use-after-free vulnerability in Google Chrome before 27.0.14…
- CVE-2013-2858Use-after-free vulnerability in the HTML5 Audio implementati…
- CVE-2013-2859Google Chrome before 27.0.1453.110 allows remote attackers t…
Are you affected by CVE-2013-2853?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST