Secret recovery via compressed-response length oracle
Published Feb 21, 2020 · Updated Aug 6, 2024
Information disclosure in compressed HTTPS web applications allows man-in-the-middle attackers to recover response secrets via length analysis. HTTP response compression combines reflected attacker-controlled input with a static secret before encryption, making correct character guesses produce measurably shorter ciphertext. Exploitation requires repeated chosen requests through a victim browser, visibility into response sizes, and a sufficiently stable page that reflects both input and a secret.
Summary
What happened
Information disclosure in compressed HTTPS web applications allows man-in-the-middle attackers to recover response secrets via length analysis. HTTP response compression combines reflected attacker-controlled input with a static secret before encryption, making correct character guesses produce measurably shorter ciphertext. Exploitation requires repeated chosen requests through a victim browser, visibility into response sizes, and a sufficiently stable page that reflects both input and a secret.
The record
- CVE
- CVE-2013-3587
- Published
- Feb 21, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- BREACH Basic proof-of-concept toolfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo