Full Report
A widespread, long-standing security flaw that allows attackers to decrypt HTTPS-protected traffic between certain device and potentially millions of websites has been uncovered by security researchers, reports Ars Technica.
Analysis Summary
# Vulnerability: FREAK Attack (Factoring RSA Export Keys)
## CVE Details
This article does not explicitly list a specific CVE identifier or CVSS score.
- CVE ID: Information not provided in the text.
- CVSS Score: Information not provided in the text.
- CWE: Information not provided in the text (Related to weak cryptographic protocols/ciphers).
## Affected Systems
- Products: Apple Safari web browsers and Google Android software (browsers built into the OS).
- Versions: Not explicitly listed, but affects systems using legacy "export grade encryption" capabilities.
- Configurations: Systems that negotiate down to weak 512-bit RSA encryption during TLS handshakes.
## Vulnerability Description
The FREAK attack exploits a legacy vulnerability stemming from "export grade encryption," which was deliberately weaker (512-bit keys) encryption mandated by the US government for products shipped outside the US decades prior. Attackers can force a connection between a client (affected browser) and a server (even modern, secure ones) to negotiate down to this weak 512-bit RSA key. This 512-bit key can then be broken using sufficient computation power, potentially costing as little as $100 per website, allowing decryption of HTTPS-protected traffic.
## Exploitation
- Status: Not evidence that the vulnerability has been exploited by hackers noted, but PoC research exists.
- Complexity: Low (breaking the 512-bit key is feasible).
- Attack Vector: Network (Requires interception of the TLS handshake).
## Impact
- Confidentiality: High (Decryption of sensitive HTTPS traffic possible).
- Integrity: Medium/High (If elements are appropriated, integrity may be compromised).
- Availability: Low (The attack focuses on decryption, not denial of service).
## Remediation
### Patches
- Google: Update released for device makers and wireless carriers.
- Apple: A fix was announced and expected to be available "next week" (from the article date of March 4, 2015).
### Workarounds
- Users are advised to update their affected systems immediately once vendor patches become available.
- **Note:** The article implies that browsers like Chrome, Microsoft browsers, and Mozilla browsers were **not** affected.
## Detection
- Indicators of Compromise: Not specified, as detection is typically based on recognizing the forced downgrade to weak cipher suites during the TLS handshake.
- Detection methods and tools: Not specified, but standard network analysis capable of inspecting TLS cipher suite negotiation could reveal attempts to force export ciphers.
## References
- Vendor Advisories: Google and Apple advisories (dates not specified).
- Relevant links:
- Ars Technica Report: hxxp://arstechnica.com/security/2015/03/freak-flaw-in-android-and-apple-devices-cripples-https-crypto-protection/
- Washington Post Explanation: hxxp://www.washingtonpost.com/blogs/the-switch/wp/2015/03/03/freak-flaw-undermines-security-for-apple-and-google-users-researchers-discover/
- The Guardian Report: hxxp://www.theguardian.com/technology/2015/03/04/freak-attack-leaves-millions-of-apple-and-google-users-vulnerable-to-hackers
- Forbes Report: hxxp://www.forbes.com/sites/thomasbrewster/2015/03/03/freak-flaw-hits-android-and-iphone-users/