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.
Published: 2013-07-10
Score: 6.8 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-2724-1 chromium-browser security update
EUVD 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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: Chrome

Published:

Updated: 2024-08-06T15:52:20.637Z

Reserved: 2013-04-11T00:00:00.000Z

Link: CVE-2013-2853

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2013-07-10T10:55:01.783

Modified: 2026-04-29T01:13:23.040

Link: CVE-2013-2853

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses