Skip to content
Fencer Intel
medium 5.9

CVE-2013-3587 json

The HTTPS protocol, as used in unspecified web applications, can encrypt compressed data without properly obfuscating the length of the une…

published 2020-02-21 6 y ago modified 2026-06-16 4 mo ago also EUVD-2013-3521

cvss
5.9
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.0%
EPSS 6.0% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

The HTTPS protocol, as used in unspecified web applications, can encrypt compressed data without properly obfuscating the length of the unencrypted data, which makes it easier for man-in-the-middle attackers to obtain plaintext secret values by observing length differences during a series of guesses in which a string in an HTTP request URL potentially matches an unknown string in an HTTP response body, aka a "BREACH" attack, a different issue than CVE-2012-4929.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-3587 updated cvss 4.3

BREACH attack against HTTP compression

  • Red Hat Enterprise Linux 5 httpd Red Hat Enterprise Linux 6 httpd, mod_ssl, httpd-tools, httpd-manual
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.05% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • security.stackexchange.com http://security.stackexchange.com/questions/20406/is-http-compression-safe#20407 referenced PoC, tagged "exploit" by a source, unverified
  • hackerone.com https://hackerone.com/reports/254895 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • n/a HTTPS protocol

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.