<story><title>OpenSSL Security Advisory: TLS heartbeat read overrun</title><url>http://www.openssl.org/news/secadv_20140407.txt</url></story><parent_chain></parent_chain><comment><author>tptacek</author><text>Ugh, that&amp;#x27;s a horrible vulnerability. We found something similar in nginx a few years ago, and the result is that you can repeatedly open up client connections and dump server memory as it changes, revealing keys and, without any real effort, authentication info and cookies.</text></comment>
<story><title>OpenSSL Security Advisory: TLS heartbeat read overrun</title><url>http://www.openssl.org/news/secadv_20140407.txt</url></story><parent_chain></parent_chain><comment><author>dmix</author><text>I had to google what &amp;quot;heartbeat extension&amp;quot; does:&lt;p&gt;&lt;pre&gt;&lt;code&gt;   DTLS is designed to secure traffic running on top of unreliable
   transport protocols.  Usually such protocols have no session
   management.  The only mechanism available at the DTLS layer to figure
   out if a peer is still alive is performing a costly renegotiation.
   If the application uses unidirectional traffic there is no other way.

   TLS is based on reliable protocols but there is not necessarily a
   feature available to keep the connection alive without continuous
   data transfer.

   The Heartbeat Extension as described in this document overcomes these
   limitations.  The user can use the new HeartbeatRequest message which
   has to be answered by the peer with a HeartbeartResponse immediately.

&lt;/code&gt;&lt;/pre&gt;
&lt;a href=&quot;https://tools.ietf.org/html/draft-ietf-tls-dtls-heartbeat-01&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;tools.ietf.org&amp;#x2F;html&amp;#x2F;draft-ietf-tls-dtls-heartbeat-01&lt;/a&gt;&lt;p&gt;Edit: here is the commit patching the bug &lt;a href=&quot;https://github.com/openssl/openssl/commit/7e840163c06c7692b796a93e3fa85a93136adbb2&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;openssl&amp;#x2F;openssl&amp;#x2F;commit&amp;#x2F;7e840163c06c7692b7...&lt;/a&gt;</text></comment>