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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-2724-1 | chromium-browser security update |
EUVD |
EUVD-2013-2792 | 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. |
References
History
No history.
Status: PUBLISHED
Assigner: Chrome
Published:
Updated: 2024-08-06T15:52:20.637Z
Reserved: 2013-04-11T00:00:00.000Z
Link: CVE-2013-2853
No data.
Status : Deferred
Published: 2013-07-10T10:55:01.783
Modified: 2025-04-11T00:51:21.963
Link: CVE-2013-2853
No data.
OpenCVE Enrichment
No data.
Weaknesses
Debian DSA
EUVD