medium
5.9
CWE
200 352
Advisory Published
CVE Published
Updated

CVE-2013-3587: Infoleak

First published: Thu Aug 08 2013(Updated: )

Angelo Prado, Neal Harris and Yoel Gluck reported [1],[2] that SSL/TLS attacks are still viable via a "BREACH" (Browser Reconnaissance &amp; Exfiltration via Adaptive Compression of Hypertext) attack, which they describe as: While CRIME was mitigated by disabling TLS/SPDY compression (and by modifying gzip to allow for explicit separation of compression contexts in SPDY), BREACH attacks HTTP responses. These are compressed using the common HTTP compression, which is much more common than TLS-level compression. This allows essentially the same attack demonstrated by Duong and Rizzo, but without relying on TLS-level compression (as they anticipated). BREACH is a category of vulnerabilities and not a specific instance affecting a specific piece of software. To be vulnerable, a web application must: * Be served from a server that uses HTTP-level compression * Reflect user-input in HTTP response bodies * Reflect a secret (such as a CSRF token) in HTTP response bodies It is important to note that the attack is agnostic to the version of TLS/SSL, and does not require TLS-layer compression. Additionally, the attack works against any cipher suite. Against a stream cipher, the attack is simpler; the difference in sizes across response bodies is much more granular in this case. If a block cipher is used, additional work must be done to align the output to the cipher text blocks. CERT has an entry describing the flaw as well [3]. Currently no CVE is assigned as MITRE is attempting to determine whether one CVE will suffice, or whether it will require multiple CVEs (one per affected product). [4] Mitigations are noted by the researchers as follows 1. Disable HTTP compression. 2. Separate the secrets from the user input. 3. Randomize the secrets in each client request. 4. Mask secrets (effectively randomizing by XORing with a random secret per request). 5. Protect web pages from CSRF attacks. 6. Obfuscate the length of web responses by adding random amounts of arbitrary bytes. [1] <a href="http://breachattack.com/">http://breachattack.com/</a> [2] <a href="http://breachattack.com/resources/BREACH%20-%20SSL,%20gone%20in%2030%20seconds.pdf">http://breachattack.com/resources/BREACH%20-%20SSL,%20gone%20in%2030%20seconds.pdf</a> [3] <a href="http://www.kb.cert.org/vuls/id/987798">http://www.kb.cert.org/vuls/id/987798</a> [4] <a href="http://www.openwall.com/lists/oss-security/2013/08/07/1">http://www.openwall.com/lists/oss-security/2013/08/07/1</a>

Credit: cret@cert.org

Affected SoftwareAffected VersionHow to fix
F5 BIG-IP Access Policy Manager>=10.1.0<=10.2.4
F5 BIG-IP Access Policy Manager>=11.0.0<=11.6.1
F5 BIG-IP Access Policy Manager>=12.0.0<=12.1.2
F5 BIG-IP Access Policy Manager=13.0.0
F5 BIG-IP Advanced Firewall Manager>=11.3.0<=11.6.1
F5 BIG-IP Advanced Firewall Manager>=12.0.0<=12.1.2
F5 BIG-IP Advanced Firewall Manager=13.0.0
F5 BIG-IP Analytics>=11.0.0<=11.6.1
F5 BIG-IP Analytics>=12.0.0<=12.1.2
F5 BIG-IP Analytics=13.0.0
F5 Big-ip Application Acceleration Manager>=11.4.0<=11.6.1
F5 Big-ip Application Acceleration Manager>=12.0.0<=12.1.2
F5 Big-ip Application Acceleration Manager=13.0.0
F5 BIG-IP Application Security Manager>=9.2.0<=9.4.8
F5 BIG-IP Application Security Manager>=10.0.0<=10.2.4
F5 BIG-IP Application Security Manager>=11.0.0<=11.6.1
F5 BIG-IP Application Security Manager>=12.0.0<=12.1.2
F5 BIG-IP Application Security Manager=13.0.0
F5 Big-ip Edge Gateway>=10.1.0<=10.2.4
F5 Big-ip Edge Gateway>=11.0.0<=11.3.0
F5 Big-ip Link Controller>=9.2.2<=9.4.8
F5 Big-ip Link Controller>=10.0.0<=10.2.4
F5 Big-ip Link Controller>=11.0.0<=11.6.1
F5 Big-ip Link Controller>=12.0.0<=12.1.2
F5 Big-ip Link Controller=13.0.0
F5 Big-ip Local Traffic Manager>=9.0.0<=9.6.1
F5 Big-ip Local Traffic Manager>=10.0.0<=10.2.4
F5 Big-ip Local Traffic Manager>=11.0.0<=11.6.1
F5 Big-ip Local Traffic Manager>=12.0.0<=12.1.2
F5 Big-ip Local Traffic Manager=13.0.0
F5 Big-ip Policy Enforcement Manager>=11.3.0<=11.6.1
F5 Big-ip Policy Enforcement Manager>=12.0.0<=12.1.2
F5 Big-ip Policy Enforcement Manager=13.0.0
F5 Big-ip Protocol Security Module>=9.4.5<=9.4.8
F5 Big-ip Protocol Security Module>=10.0.0<=10.2.4
F5 Big-ip Protocol Security Module>=11.0.0<=11.4.1
F5 Big-ip Wan Optimization Manager>=10.0.0<=10.2.4
F5 Big-ip Wan Optimization Manager>=11.0.0<=11.3.0
F5 Big-ip Webaccelerator>=9.4.0<=9.4.8
F5 Big-ip Webaccelerator>=10.0.0<=10.2.4
F5 Big-ip Webaccelerator>=11.0.0<=11.3.0
F5 FirePass>=6.0.0<=6.1.0
F5 FirePass=7.0.0
F5 Arx>=5.0.0<=5.3.1
F5 Arx>=6.0.0<=6.4.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is CVE-2013-3587?

    CVE-2013-3587 is a vulnerability that allows man-in-the-middle attackers to obtain plaintext secret values by observing length differences during a series of guesses.

  • Which web applications are affected by CVE-2013-3587?

    The vulnerability affects F5 BIG-IP Access Policy Manager, Advanced Firewall Manager, Analytics, Application Acceleration Manager, Application Security Manager, Edge Gateway, Local Traffic Manager, Policy Enforcement Manager, Protocol Security Module, Wan Optimization Manager, Webaccelerator, FirePass, and Arx.

  • How severe is CVE-2013-3587?

    The severity of CVE-2013-3587 is medium with a CVSS score of 5.9.

  • How can I mitigate CVE-2013-3587?

    To mitigate the vulnerability, ensure that your web applications and systems are using a secure encryption and compression algorithm and implement proper obfuscation techniques.

  • Where can I find more information about CVE-2013-3587?

    You can find more information about CVE-2013-3587 at the following references: http://breachattack.com/, http://github.com/meldium/breach-mitigation-rails, and http://security.stackexchange.com/questions/20406/is-http-compression-safe#20407

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203