)]}'
{"security-notes/OSSN-0045":[{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"0d0b08810031a7cc18da7dbce5b554908bc043be","unresolved":false,"context_lines":[{"line_number":32,"context_line":"send it back in the server HELLO message."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Export grade ciphers are a legacy of a time when the US government prohibited"},{"line_number":35,"context_line":"the export of cryptographic ciphers which were stronger than a certain threshold"},{"line_number":36,"context_line":"(512 bit RSA, 40 bit symmetric cipher). Today these ciphers are easily and"},{"line_number":37,"context_line":"quickly crackable using commodity hardware or cloud resources."},{"line_number":38,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"9a80dd14_41d43647","line":35,"updated":"2015-03-10 15:49:45.000000000","message":"If we\u0027re calling out the threshold, I think we should say \"stronger than the threshold of 512 bit RSA, 40....\"","commit_id":"b7227f91e552e84c468792f444962f139c19e4d3"},{"author":{"_account_id":11861,"name":"Travis McPeak","email":"tmcpeak@us.ibm.com","username":"travis-mcpeak"},"change_message_id":"b0e00bd4c40477e2a0e34b1481d48b5da11d9c25","unresolved":false,"context_lines":[{"line_number":32,"context_line":"send it back in the server HELLO message."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Export grade ciphers are a legacy of a time when the US government prohibited"},{"line_number":35,"context_line":"the export of cryptographic ciphers which were stronger than a certain threshold"},{"line_number":36,"context_line":"(512 bit RSA, 40 bit symmetric cipher). Today these ciphers are easily and"},{"line_number":37,"context_line":"quickly crackable using commodity hardware or cloud resources."},{"line_number":38,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"9a80dd14_09ffc0ab","line":35,"in_reply_to":"9a80dd14_41d43647","updated":"2015-03-10 17:20:14.000000000","message":"Done","commit_id":"b7227f91e552e84c468792f444962f139c19e4d3"},{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"0d0b08810031a7cc18da7dbce5b554908bc043be","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"### Recommended Actions ###"},{"line_number":40,"context_line":"Since this is a vulnerability in client logic the best option is to ensure that"},{"line_number":41,"context_line":"all clients update to the latest version of the affected library. Since it is"},{"line_number":42,"context_line":"unfeasible to assume that all clients have updated, we should also mitigate this"},{"line_number":43,"context_line":"as possible on the TLS server-side."},{"line_number":44,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"9a80dd14_214ca276","line":41,"updated":"2015-03-10 15:49:45.000000000","message":"I don\u0027t see the version of the \u0027latest affected library\u0027. Can we call this out?","commit_id":"b7227f91e552e84c468792f444962f139c19e4d3"},{"author":{"_account_id":11861,"name":"Travis McPeak","email":"tmcpeak@us.ibm.com","username":"travis-mcpeak"},"change_message_id":"b0e00bd4c40477e2a0e34b1481d48b5da11d9c25","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"### Recommended Actions ###"},{"line_number":40,"context_line":"Since this is a vulnerability in client logic the best option is to ensure that"},{"line_number":41,"context_line":"all clients update to the latest version of the affected library. Since it is"},{"line_number":42,"context_line":"unfeasible to assume that all clients have updated, we should also mitigate this"},{"line_number":43,"context_line":"as possible on the TLS server-side."},{"line_number":44,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"9a80dd14_c9904851","line":41,"in_reply_to":"9a80dd14_214ca276","updated":"2015-03-10 17:20:14.000000000","message":"It really depends, FREAK can apply to many TLS implementations, one of which is OpenSSL.  Even OpenSSL has three main versions that people are currently using: 0.9.8, 1.0.0, and 1.0.1.  Calling out specific versions for all three of these will be wordy.  How about I\u0027ll add a link and the bottom to the OpenSSL advisory and mention it here?","commit_id":"b7227f91e552e84c468792f444962f139c19e4d3"},{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"0d0b08810031a7cc18da7dbce5b554908bc043be","unresolved":false,"context_lines":[{"line_number":43,"context_line":"as possible on the TLS server-side."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"To mitigate the FREAK attack on the server side, we need to remove support for"},{"line_number":46,"context_line":"any ciphers which are weak. This is to prevent a MITM from forcing the client to"},{"line_number":47,"context_line":"chose a weak cipher. In particular we need to remove support for any export"},{"line_number":48,"context_line":"grade ciphers, which are especially weak."},{"line_number":49,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"9a80dd14_01eebeb4","line":46,"updated":"2015-03-10 15:49:45.000000000","message":"I\u0027d recommend changing client to session as the wording here suggests the MITM communication is to the client; session will reinforce that the end-to-end communication (even after negotiated hello) is insecure.","commit_id":"b7227f91e552e84c468792f444962f139c19e4d3"},{"author":{"_account_id":11861,"name":"Travis McPeak","email":"tmcpeak@us.ibm.com","username":"travis-mcpeak"},"change_message_id":"b0e00bd4c40477e2a0e34b1481d48b5da11d9c25","unresolved":false,"context_lines":[{"line_number":43,"context_line":"as possible on the TLS server-side."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"To mitigate the FREAK attack on the server side, we need to remove support for"},{"line_number":46,"context_line":"any ciphers which are weak. This is to prevent a MITM from forcing the client to"},{"line_number":47,"context_line":"chose a weak cipher. In particular we need to remove support for any export"},{"line_number":48,"context_line":"grade ciphers, which are especially weak."},{"line_number":49,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"9a80dd14_4908d891","line":46,"in_reply_to":"9a80dd14_01eebeb4","updated":"2015-03-10 17:20:14.000000000","message":"Session is actually not accurate in this case.  If the session key were compromised when keys are periodically rotated the vulnerability would end. In this case the pre-shared master is compromised which is worse than session keys.","commit_id":"b7227f91e552e84c468792f444962f139c19e4d3"},{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"0d0b08810031a7cc18da7dbce5b554908bc043be","unresolved":false,"context_lines":[{"line_number":51,"context_line":"Two useful solutions exist for this: SSL Server Test at Qualys SSL Labs can be"},{"line_number":52,"context_line":"used to scan any web accessible endpoints, and SSLScan is a command line tool"},{"line_number":53,"context_line":"which iterates through all ciphers and attempts a connection to a specified"},{"line_number":54,"context_line":"server using that suite. Please see \"tools\" below for links to both."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"The specific steps required to configure which cipher suites are supported in a"},{"line_number":57,"context_line":"TLS deployment depend on the software and configuration, and are beyond the"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"9a80dd14_61577acb","line":54,"updated":"2015-03-10 15:49:45.000000000","message":"\"...using that suite.\" Which suite? A user-specified one? Or a discrete one we can call out?","commit_id":"b7227f91e552e84c468792f444962f139c19e4d3"},{"author":{"_account_id":11861,"name":"Travis McPeak","email":"tmcpeak@us.ibm.com","username":"travis-mcpeak"},"change_message_id":"b0e00bd4c40477e2a0e34b1481d48b5da11d9c25","unresolved":false,"context_lines":[{"line_number":51,"context_line":"Two useful solutions exist for this: SSL Server Test at Qualys SSL Labs can be"},{"line_number":52,"context_line":"used to scan any web accessible endpoints, and SSLScan is a command line tool"},{"line_number":53,"context_line":"which iterates through all ciphers and attempts a connection to a specified"},{"line_number":54,"context_line":"server using that suite. Please see \"tools\" below for links to both."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"The specific steps required to configure which cipher suites are supported in a"},{"line_number":57,"context_line":"TLS deployment depend on the software and configuration, and are beyond the"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"9a80dd14_8971f0e2","line":54,"in_reply_to":"9a80dd14_61577acb","updated":"2015-03-10 17:20:14.000000000","message":"Done","commit_id":"b7227f91e552e84c468792f444962f139c19e4d3"},{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"257403aec011ca5ed1f1512e9fdc94f9fcea054c","unresolved":false,"context_lines":[{"line_number":2,"context_line":"---"},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"### Summary ###"},{"line_number":5,"context_line":"Some client-side libraries including unpatched versions of OpenSSL contain a"},{"line_number":6,"context_line":"vulnerability which can allow a man-in-the-middle (MITM) to force a TLS version"},{"line_number":7,"context_line":"downgrade. Even though this vulnerability exists in the client side, an attack"},{"line_number":8,"context_line":"known as FREAK is exploitable when TLS servers offer weak cipher choices. This"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_28c0f529","line":5,"updated":"2015-03-10 21:35:48.000000000","message":"nit: probably want to set off the \u0027including unpatched version of OpenSSL\u0027 - maybe with commas?","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"},{"author":{"_account_id":11861,"name":"Travis McPeak","email":"tmcpeak@us.ibm.com","username":"travis-mcpeak"},"change_message_id":"5f0d07312cc59dea437513bd1e74ca353566208a","unresolved":false,"context_lines":[{"line_number":2,"context_line":"---"},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"### Summary ###"},{"line_number":5,"context_line":"Some client-side libraries including unpatched versions of OpenSSL contain a"},{"line_number":6,"context_line":"vulnerability which can allow a man-in-the-middle (MITM) to force a TLS version"},{"line_number":7,"context_line":"downgrade. Even though this vulnerability exists in the client side, an attack"},{"line_number":8,"context_line":"known as FREAK is exploitable when TLS servers offer weak cipher choices. This"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_24356246","line":5,"in_reply_to":"9a80dd14_28c0f529","updated":"2015-03-11 13:16:54.000000000","message":"Done","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"},{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"257403aec011ca5ed1f1512e9fdc94f9fcea054c","unresolved":false,"context_lines":[{"line_number":7,"context_line":"downgrade. Even though this vulnerability exists in the client side, an attack"},{"line_number":8,"context_line":"known as FREAK is exploitable when TLS servers offer weak cipher choices. This"},{"line_number":9,"context_line":"security note provides guidance to mitigate the FREAK attack on the server side,"},{"line_number":10,"context_line":"so that TLS provides reasonable security for even un-patched clients."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"### Affected Services / Software ###"},{"line_number":13,"context_line":"Any and all insecurely configured TLS endpoints including Horizon and OpenStack"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_c88759b5","line":10,"updated":"2015-03-10 21:35:48.000000000","message":"First line uses unpatched, this has a hyphen - we should probably be consistent.","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"},{"author":{"_account_id":11861,"name":"Travis McPeak","email":"tmcpeak@us.ibm.com","username":"travis-mcpeak"},"change_message_id":"5f0d07312cc59dea437513bd1e74ca353566208a","unresolved":false,"context_lines":[{"line_number":7,"context_line":"downgrade. Even though this vulnerability exists in the client side, an attack"},{"line_number":8,"context_line":"known as FREAK is exploitable when TLS servers offer weak cipher choices. This"},{"line_number":9,"context_line":"security note provides guidance to mitigate the FREAK attack on the server side,"},{"line_number":10,"context_line":"so that TLS provides reasonable security for even un-patched clients."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"### Affected Services / Software ###"},{"line_number":13,"context_line":"Any and all insecurely configured TLS endpoints including Horizon and OpenStack"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_441176ab","line":10,"in_reply_to":"9a80dd14_c88759b5","updated":"2015-03-11 13:16:54.000000000","message":"Done","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"},{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"257403aec011ca5ed1f1512e9fdc94f9fcea054c","unresolved":false,"context_lines":[{"line_number":11,"context_line":""},{"line_number":12,"context_line":"### Affected Services / Software ###"},{"line_number":13,"context_line":"Any and all insecurely configured TLS endpoints including Horizon and OpenStack"},{"line_number":14,"context_line":"APIs."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"### Discussion ###"},{"line_number":17,"context_line":"TLS connections are established by a process known as a TLS handshake. During"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_f3c96e7a","line":14,"updated":"2015-03-10 21:35:48.000000000","message":"I\u0027d really like to get a bit more concrete around determining this. I\u0027m curious what others think, but personally I\u0027d like to see the tools or methodology mentioned here to be able to determine what is vulnerable - \"if you fail this test\" or \"if you see these cypher suites in the output of X\". If the consensus is that\u0027s too general to put in here that\u0027s fine as well.","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"},{"author":{"_account_id":11861,"name":"Travis McPeak","email":"tmcpeak@us.ibm.com","username":"travis-mcpeak"},"change_message_id":"5f0d07312cc59dea437513bd1e74ca353566208a","unresolved":false,"context_lines":[{"line_number":11,"context_line":""},{"line_number":12,"context_line":"### Affected Services / Software ###"},{"line_number":13,"context_line":"Any and all insecurely configured TLS endpoints including Horizon and OpenStack"},{"line_number":14,"context_line":"APIs."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"### Discussion ###"},{"line_number":17,"context_line":"TLS connections are established by a process known as a TLS handshake. During"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_049a1e14","line":14,"in_reply_to":"9a80dd14_627d97b1","updated":"2015-03-11 13:16:54.000000000","message":"Good point, I\u0027ve now copied verbatim what Bryan put in his POODLE note, except I changed SSL to TLS.","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"},{"author":{"_account_id":11716,"name":"Tim Kelsey","email":"timothy.kelsey@uk.ibm.com","username":"tkelsey"},"change_message_id":"20b10019c572b0b03691e700f762c6d18af7677f","unresolved":false,"context_lines":[{"line_number":11,"context_line":""},{"line_number":12,"context_line":"### Affected Services / Software ###"},{"line_number":13,"context_line":"Any and all insecurely configured TLS endpoints including Horizon and OpenStack"},{"line_number":14,"context_line":"APIs."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"### Discussion ###"},{"line_number":17,"context_line":"TLS connections are established by a process known as a TLS handshake. During"}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_627d97b1","line":14,"in_reply_to":"9a80dd14_f3c96e7a","updated":"2015-03-11 09:45:21.000000000","message":"I thought we had a specific syntax for this section? or has that been relaxed","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"},{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"257403aec011ca5ed1f1512e9fdc94f9fcea054c","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"### Recommended Actions ###"},{"line_number":40,"context_line":"Since this is a vulnerability in client logic, the best option is to ensure that"},{"line_number":41,"context_line":"all clients update to the latest version of the affected library. For more"},{"line_number":42,"context_line":"details about upgrading OpenSSL please see the link to the OpenSSL advisory in"},{"line_number":43,"context_line":"the \"Further discussion\" section below. Since it is unfeasible to assume that"},{"line_number":44,"context_line":"all clients have updated, we should also mitigate this on the TLS server-side."}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_b3861612","line":41,"updated":"2015-03-10 21:35:48.000000000","message":"clients but not servers?","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"},{"author":{"_account_id":11861,"name":"Travis McPeak","email":"tmcpeak@us.ibm.com","username":"travis-mcpeak"},"change_message_id":"5f0d07312cc59dea437513bd1e74ca353566208a","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":"### Recommended Actions ###"},{"line_number":40,"context_line":"Since this is a vulnerability in client logic, the best option is to ensure that"},{"line_number":41,"context_line":"all clients update to the latest version of the affected library. For more"},{"line_number":42,"context_line":"details about upgrading OpenSSL please see the link to the OpenSSL advisory in"},{"line_number":43,"context_line":"the \"Further discussion\" section below. Since it is unfeasible to assume that"},{"line_number":44,"context_line":"all clients have updated, we should also mitigate this on the TLS server-side."}],"source_content_type":"application/octet-stream","patch_set":5,"id":"9a80dd14_a480728c","line":41,"in_reply_to":"9a80dd14_b3861612","updated":"2015-03-11 13:16:54.000000000","message":"Yeah, this is a client-side vulnerability.  Updating server versions of OpenSSL won\u0027t prevent this.","commit_id":"856d1979067a4c9677b2dbe9de266a5fd3eefd9d"}]}