CVE-2013-2853 describes a vulnerability in Google Chrome versions prior to 28.0.1500.71, where its HTTPS implementation failed to properly terminate headers with the expected carriage return and newline sequence. This flaw allows man-in-the-middle attackers to potentially truncate headers, leading to an unspecified impact. With a CVSS score of 6.8, it is considered a medium-severity vulnerability, requiring medium attack complexity and potentially impacting confidentiality, integrity, and availability. There is no evidence of active exploitation, public exploit code, or significant community discussion surrounding this CVE.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
<= 28.0.1500.70CPE matchmatch criteria | cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* | ||
28.0.1500.0CPE matchmatch criteria | cpe:2.3:a:google:chrome:28.0.1500.0:*:*:*:*:*:*:* | ||
28.0.1500.2CPE matchmatch criteria | cpe:2.3:a:google:chrome:28.0.1500.2:*:*:*:*:*:*:* | ||
28.0.1500.3CPE matchmatch criteria | cpe:2.3:a:google:chrome:28.0.1500.3:*:*:*:*:*:*:* | ||
28.0.1500.4CPE matchmatch criteria | cpe:2.3:a:google:chrome:28.0.1500.4:*:*:*:*:*:*:* |
CVSS version used by this source: 2.0
AV:N/AC:M/Au:N/C:P/I:P/A:P
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.0 Bluesky, 0.0 Mastodon, and 0.2 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.0 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.