Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

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,…

Medium6.8EPSS 1.1%
Published
Updated
Reserved
Assigned by
Chrome

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.

Scores

CVSS scores of CVE-2013-2853, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified2.0Medium6.8AV:N/AC:M/Au:N/C:P/I:P/A:P
EPSS (exploitation in 30 days)
1.1% · top 34% of all CVEs (4 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.8.

Weakness

  • n/a

Affected products

  • n/a

    • affected n/a

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2013-2853 badge
[![CVE-2013-2853](https://trackcve.app/badge/CVE-2013-2853.svg)](https://trackcve.app/cve/CVE-2013-2853)

Record last updated .