{"id":29622,"date":"2015-03-09T20:46:31","date_gmt":"2015-03-10T00:46:31","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/apple-google-users-at-risk-from-freak-flaw.php"},"modified":"2015-03-09T20:46:31","modified_gmt":"2015-03-10T00:46:31","slug":"apple-google-users-at-risk-from-freak-flaw","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/apple-google-users-at-risk-from-freak-flaw.php","title":{"rendered":"Apple, Google users at risk from FREAK flaw"},"content":{"rendered":"<p><p>    A major security flaw has been discovered in the Secure Sockets    Layer\/Transport Layer Security (SSL\/TLS) cryptographic    protocols, leaving users of Google and Apple devices open to    attack when visiting purportedly secure websites.  <\/p>\n<p>    Technology companies are now rushing to put out fixes for the    FREAK    attack, disclosed by researchers today.  <\/p>\n<p>    The vulnerability in the SSL\/TLS secure communications    protocols allows attackers to intercept HTTPS connections    between vulnerable clients and servers - which researchers    revealed included web browsers on Android and Apple    smartphones.  <\/p>\n<p>    Attackers could then force the site to downgrade to weak,    so-called \"export-grade\" cryptography, which could be easily    cracked in order to decrypt web traffic, in turn allowing    attackers to steal passwords and other sensitive information.  <\/p>\n<p>    The flaw has been around since the late 1990s, stemming from a    former US government policy which had banned the export of    strong encryption.  <\/p>\n<p>    The policy - which was ditched in 1999 - meant weaker    \"export-grade\" products were shipped to customers outside of    the US.  <\/p>\n<p>    However, the weaker keys continued to be used by software    companies after the policy was canned, going unnoticed until it    was discovered this year by thegroup of cryptographers at INRIA,    Microsoft Research and IMDEA.  <\/p>\n<p>    The \"FREAK name stands for 'factoring attack on RSA-EXPORT    keys'. The keys used in the export-grade encryption had a    length of 512 bits - which is considered incredibly weak in the    current age thanks to rapid increases in computing power -    allowing attackers to easily guess the key.  <\/p>\n<p>    \"This bug causes them to accept RSA export-grade keys even when    the client didn't ask for export-grade RSA,\" cryptographer    Matthew Green wrote in ablog    post.  <\/p>\n<p>    \"The impact of this bug can be quite nasty: it admits a 'man in    the middle' attack whereby an active attacker can force down    the quality of a connection, provided that the client is    vulnerable and the server supports export RSA.\"  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>See the original post:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.itnews.com.au\/News\/401200,apple-google-users-at-risk-from-freak-flaw.aspx?utm_source=feed&utm_medium=rss&utm_campaign=iTnews+\/RK=0\/RS=EtIx6MVtNPppIDByX6EYBu6F8VU-\" title=\"Apple, Google users at risk from FREAK flaw\">Apple, Google users at risk from FREAK flaw<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> A major security flaw has been discovered in the Secure Sockets Layer\/Transport Layer Security (SSL\/TLS) cryptographic protocols, leaving users of Google and Apple devices open to attack when visiting purportedly secure websites. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1600],"tags":[],"class_list":["post-29622","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29622"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=29622"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29622\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=29622"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=29622"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=29622"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}