FREAK

FREAK ("Factoring RSA Export Keys") is a security exploit of a cryptographic weakness in the SSL/TLS protocols introduced decades earlier for compliance with U.S. cryptography export regulations. These involved limiting exportable software to use only public key pairs with RSA moduli of 512 bits or less (so-called RSA_EXPORT keys), with the intention of allowing them to be broken easily by the NSA, but not by other organizations with lesser computing resources. However, by the early 2010s, increases in computing power meant that they could be broken by anyone with access to relatively modest computing resources using the well-known Number Field Sieve algorithm, using as little as $100 of cloud computing services. Combined with the ability of a man-in-the-middle to manipulate the initial cipher suite negotiation between the endpoints in the connection and the fact that the Finished hash only depended on the master secret, this meant that a man-in-the-middle, with only a modest amount of computation could break the security of any website that allowed the use of 512-bit export-grade keys. While the exploit was only discovered in 2015, its underlying vulnerabilities had been present for many years, dating back to the 1990s.

Vulnerability

The flaw was found by researchers from IMDEA, INRIA and Microsoft Research.[1] The FREAK attack in OpenSSL has the CVE identifier CVE-2015-0204.[2]

Vulnerable software and devices included Apple's Safari web browser, the default browser in Google's Android phone operating system, Microsoft's Internet Explorer, and OpenSSL.[3][1] Microsoft has also stated that its SChannel implementation of transport-layer encryption is vulnerable to a version of the FREAK attack in all versions of Microsoft Windows.[4] The CVE ID for Microsoft's vulnerability in SChannel is CVE-2015-1637.[5] The CVE ID for Apple's vulnerability in Secure Transport is CVE-2015-1067.[6]

Sites affected by the vulnerability included the U.S. federal government websites fbi.gov, whitehouse.gov and nsa.gov,[7] with around 36% of HTTPS-using websites tested by one security group shown as being vulnerable to the exploit.[8] Based on geolocation analysis using IP2Location LITE, 35% of vulnerable servers are located in the USA.[9]

Press reports of the exploit have described its effects as "potentially catastrophic"[10] and an "unintended consequence" of U.S. government efforts to control the spread of cryptographic technology.[7]

As of March 2015, vendors were in the process of releasing new software that would fix the flaw.[7][8] On March 9, 2015, Apple released security updates for both iOS 8 and OS X operating systems which fixed this flaw.[11][12] On March 10, 2015, Microsoft released a patch which fixed this vulnerability for all supported versions of Windows (Server 2003, Vista and later).[13] Google Chrome 41 and Opera 28 has also mitigated against this flaw.[14] Mozilla Firefox is not vulnerable against this flaw.[15]

See also

References

External links