SECADV 20140407 - Revision history

Tjh: correct page name

2014-06-05T23:30:13Z

correct page name

Tjh: moved SECADV 2014047 to SECADV 20140407: get the name right

2014-06-05T23:29:06Z

moved SECADV 2014047 to SECADV 20140407: get the name right

Jwalton: Cloudfare -> Cloudflare.

2014-04-27T21:12:31Z

Cloudfare -> Cloudflare.

Matt: Typo correction

2014-04-27T11:50:28Z

Typo correction

Tjh at 04:21, 27 April 2014

2014-04-27T04:21:25Z

Tjh: Initial list of useful links and summary details for heartbeat advisory

2014-04-27T04:20:43Z

Initial list of useful links and summary details for heartbeat advisory

New page

= SECADV_2014047 =

A missing bounds check in the handling of the TLS heartbeat extension can be
used to reveal up to 64k of memory to a connected client or server.

{| class="wikitable" border="1"
|-
! scope="col" | Date
! scope="col" | Advisory
! scope="col" | Description
! scope="col" | CVE
! scope="col" | Affected Versions
! scope="col" | Fixed In Versions
|-
| 07-Apr-2014
| [https://www.openssl.org/news/secadv_20140407.txt SECADV_20140477]
| TLS heartbeat read overrun
| [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160 CVE-2014-1060]
| OpenSSL-1.0.1a to OpenSSL-1.0.1f
OpenSSL-1.0.2 betas
| OpenSSL-1.0.1g
OpenSSL-1.0.2-beta2
| [[SECADV_2014047]]
|}

== Abstract ==

Due to a missing / incorrect bounds check in the code it is possible to return chunks of memory from a TLS peer (client or server)
by sending invalid requests which are incorrectly processed.

The memory returned may contain sensitive information such as the private key, account names and/or passwords.

== Technical Details ==

Either party in an SSL/TLS channel can request a heartbeat response from the peer.
This means a client and send a request to a server or a server can send a request to a client making each vulnerable to attach from the other end.

== Solutions and Workarounds ==

:* Upgrade to OpenSSL 1.0.1g.
:** This is the recommended option from the OpenSSL team.
:* Rebuild your affected OpenSSL release with the heartbeat feature disabled
:** This is as simple as a recompilation with -DOPENSSL_NO_HEARTBEATS
:* Block the heartbeat processing in your application code
:** [https://gist.github.com/t-j-h/11337380 heartbeat_block.c] Example application code showing msg_cb use to block heartbeat

== Detecting Vulnerability ==

:* [https://gist.github.com/robstradling/10363389 heartbleed.c] Rob Stradling
::* C code exampling using OpenSSL library to detect if a server is vulnerable. Requires completed handshake prior to sending invalid heartbeat probe.
:* [https://github.com/noxxi/p5-scripts/blob/master/check-ssl-heartbleed.pl check-ssl-heartbleed.pl] Steffen Ullrich
::* Standalone perl script to detect if a server is vulnerable. Sends a ClientHello message and then an invalid heartbeat probe without waiting for the handshake to complete.
:* [https://code.google.com/p/mike-bland/source/browse/heartbleed/heartbleed_test.c heartbleed_test.c] Mike Bland ([https://github.com/openssl/openssl/pull/81 git pull request])
::* Regression / Unit Test Suite
:* [http://blog.meldium.com/home/2014/4/10/testing-for-reverse-heartbleed Testing For Reverse HeartBleed]
:* [https://github.com/ah8r/cardiac-arrest Cardiac Arrest]
::* Standalone Python script to detect if a server is vulnerable.

== References ==

:* [http://heartbleed.com/ '''HeartBleed'''] [http://www.codenomicon.com/ CodeNomicon ]
:* [https://gist.github.com/epixoip/10570627 '''Cloudfare Challenge Writeup'''] Jeremi M Gosney
:* [https://bugzilla.redhat.com/attachment.cgi?id=883475 RedHat fix commit]
:* [https://plus.google.com/+MarkJCox/posts/TmCbp3BhJma Timeline] Mark J Cox
:* [http://www.smh.com.au/it-pro/security-it/heartbleed-disclosure-timeline-who-knew-what-and-when-20140415-zqurk.html Heartbleed disclosure timeline: who knew what and when] Sydney Morning Herald
:* [http://www.hut3.net/blog/cns---networks-security/2014/04/14/bugs-in-heartbleed-detection-scripts- Bugs in Heartbleed detection scripts]

@@ Line 1: / Line 1: @@
-= SECADV_2014047 =
+= SECADV_20140407 =
 A missing bounds check in the handling of the TLS heartbeat extension can be
@@ Line 14: / Line 14: @@
 |-
 | 07-Apr-2014
-| [https://www.openssl.org/news/secadv_20140407.txt SECADV_20140477]
+| [https://www.openssl.org/news/secadv_20140407.txt SECADV_20140407]
 | TLS heartbeat read overrun
 | [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160 CVE-2014-1060]

← Older revision	Revision as of 23:29, 5 June 2014
(No difference)

@@ Line 59: / Line 59: @@
 :* [http://heartbleed.com/ '''HeartBleed'''] [http://www.codenomicon.com/ CodeNomicon ]
-:* [https://gist.github.com/epixoip/10570627 '''Cloudfare Challenge Writeup'''] Jeremi M Gosney
+:* [https://gist.github.com/epixoip/10570627 '''Cloudflare Challenge Writeup'''] Jeremi M Gosney
 :* [https://bugzilla.redhat.com/attachment.cgi?id=883475 RedHat fix commit]
 :* [https://plus.google.com/+MarkJCox/posts/TmCbp3BhJma Timeline] Mark J Cox
 :* [http://www.smh.com.au/it-pro/security-it/heartbleed-disclosure-timeline-who-knew-what-and-when-20140415-zqurk.html Heartbleed disclosure timeline: who knew what and when] Sydney Morning Herald
 :* [http://www.hut3.net/blog/cns---networks-security/2014/04/14/bugs-in-heartbleed-detection-scripts- Bugs in Heartbleed detection scripts]

@@ Line 33: / Line 33: @@
 Either party in an SSL/TLS channel can request a heartbeat response from the peer.
-This means a client and send a request to a server or a server can send a request to a client making each vulnerable to attach from the other end.
+This means a client can send a request to a server or a server can send a request to a client making each vulnerable to attach from the other end.
 == Solutions and Workarounds ==

@@ Line 21: / Line 21: @@
 | OpenSSL-1.0.1g
 OpenSSL-1.0.2-beta2
 |}