CVE-2013-3587
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure.
- Exploit odds
- 6.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 6.0% in the next 30 days (EPSS).
- Severity: 5.9 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 6.0% · EPSS, next 30 days
- Weakness
- CWE-200 · Information exposure
- Record status
- Modified
Affected
- f5 big-ip Access Policy Manager ≤ 10.2.4
- f5 big-ip Access Policy Manager ≤ 11.6.1
- f5 big-ip Access Policy Manager ≤ 12.1.2
- f5 big-ip Access Policy Manager 13.0.0
- f5 big-ip Advanced Firewall Manager ≤ 11.6.1
- f5 big-ip Advanced Firewall Manager ≤ 12.1.2
- f5 big-ip Advanced Firewall Manager 13.0.0
- f5 big-ip Analytics ≤ 11.6.1
Attack profile CVSS 3.1 · 5.9
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2013-3587.md and follow it. Check whether this project is affected by CVE-2013-3587. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://breachattack.com/
- http://github.com/meldium/breach-mitigation-rails
- 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
- http://www.kb.cert.org/vuls/id/987798
- https://bugzilla.redhat.com/show_bug.cgi?id=995168
- https://hackerone.com/reports/254895
- https://lists.apache.org/thread.html/r7f0e9cfd166934172d43ca4c272b8bdda4a343036229d9937affd1e1%40%3Cdev.httpd.apache.org%3E
- https://support.f5.com/csp/article/K14634
- https://www.blackhat.com/us-13/briefings.html#Prado
- https://www.djangoproject.com/weblog/2013/aug/06/breach-and-django/
- http://breachattack.com/
- http://github.com/meldium/breach-mitigation-rails
- 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
- http://www.kb.cert.org/vuls/id/987798
- https://bugzilla.redhat.com/show_bug.cgi?id=995168
- https://hackerone.com/reports/254895
- https://lists.apache.org/thread.html/r7f0e9cfd166934172d43ca4c272b8bdda4a343036229d9937affd1e1%40%3Cdev.httpd.apache.org%3E
- https://support.f5.com/csp/article/K14634
- https://www.blackhat.com/us-13/briefings.html#Prado
- https://www.djangoproject.com/weblog/2013/aug/06/breach-and-django/