CVE-2013-3587
- State
- Published
- Severity
- Not scored
- Published
- Feb 21, 2020
- Updated
- Aug 6, 2024
- Reserved
- May 21, 2013
Description
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.
Scores
The record has no CVSS score.
Weaknesses
The record names no weakness.
Affected Products
| Product | Versions |
|---|---|
HTTPS protocoln/a |
|
References
- http://breachattack.com/
- http://security.stackexchange.com/questions/20406/is-http-compression-safe#20407
- http://slashdot.org/story/13/08/05/233216
- http://www.iacr.org/cryptodb/archive/2002/FSE/3091/3091.pdf
- https://www.blackhat.com/us-13/briefings.html#Prado
- http://github.com/meldium/breach-mitigation-rails
- https://www.djangoproject.com/weblog/2013/aug/06/breach-and-django/
- http://www.kb.cert.org/vuls/id/987798
- https://hackerone.com/reports/254895
- https://bugzilla.redhat.com/show_bug.cgi?id=995168
- https://support.f5.com/csp/article/K14634
- [httpd-dev] 20210409 GSOC project Idea- fix for CVE-2013-3587mailing-list
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.