The heartbleed web site indicates that openssl is responding to heartbeat 
requests during the handshake.
http://heartbleed.com/
"... heartbeat request can be sent and is replied to during the handshake phase 
of the protocol. "

Doesn't RFC6520 clause 3 indicate that a received heartbeat request should be 
discarded during the handshake?
https://tools.ietf.org/html/rfc6520

"  However, a HeartbeatRequest message SHOULD NOT be sent during
   handshakes.  If a handshake is initiated while a HeartbeatRequest is
   still in flight, the sending peer MUST stop the DTLS retransmission
   timer for it.  The receiving peer SHOULD discard the message
   silently, if it arrives during the handshake.  In case of DTLS,
   HeartbeatRequest messages from older epochs SHOULD be discarded."

**The receiving peer SHOULD discard the message silently, if it arrives during 
the handshake.**

<t1_lib.c> tls1_heartbeat() and <dt_both.c> dtls1_heartbeat() already have a 
check for "... and no handshake in progress".
Should a similar check be added to  <t1_lib.c> tls1_process_heartbeat() and 
<d1_both.c> dtls1_process_heartbeat() ?


-----Original Message-----
From: [email protected] [mailto:[email protected]] 
On Behalf Of OpenSSL
Sent: Monday, April 07, 2014 4:31 PM
To: [email protected]; [email protected]
Subject: OpenSSL Security Advisory

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

OpenSSL Security Advisory [07 Apr 2014]
========================================

TLS heartbeat read overrun (CVE-2014-0160) 
==========================================

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.

Only 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including 1.0.1f and 
1.0.2-beta1.

Thanks for Neel Mehta of Google Security for discovering this bug and to Adam 
Langley <[email protected]> and Bodo Moeller <[email protected]> for preparing 
the fix.

Affected users should upgrade to OpenSSL 1.0.1g. Users unable to immediately 
upgrade can alternatively recompile OpenSSL with -DOPENSSL_NO_HEARTBEATS.

1.0.2 will be fixed in 1.0.2-beta2.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJTQt1bAAoJENNXdQf6QOniGhkP/AjjZgV+g7ZyxnxdnvA2+sdV
sxNso208Cod8DKnDONtXHuPTkTFfyHl72FM1ea99woe3X6JWj3PyiZGvSfeo4Jj/
QiDJvvcHc5Xq00gAr6MIarhMJbRtYkM+Th6PPXyqODYcb/pDoqy5VWo/R9QkZTPn
zaiXPyapJB/qSYo4UqXWerT9YTLdYmiro//kQN0U/SedF/fNz4CEBcMyz6z7YJAC
LFoE6Vf54PAkNvxjcX9ugIKluBMk5YONRG8PB0X/UDwf9Kj4L6OTT51x1yeFw3Sg
GzTqvKD+2JWzFDCcfJULRCSCEwHhKbjR7n3sI1RPaaEWp5E63+9HSMRYjVOFIwt/
OTrMPbW1BEiX0A7NB7HSrrvddnYd3sz8A44v00oesr+XaW5nyu79IndQwLhPkKYF
Dkb67quw/tfV6Y1r4sETqSd2FrM7MpFzltywMKzVKWNpMSwOAWSBGUl7VH0m84Ty
zAufUSEnYIA3dMC2DnHie+ot4WnjJlTErBmfUb/QNbNYDt0vjhS60oydP1NJ8AlG
aoUK7mslOlVCauAIeGNbi4PzJ+LvWYmyFFGT+M1/UOBZFFvG7jsReBjTIu9dg3Za
S7NE7CeMvRRpOEm1+T9L8a26/c6C9dwF7JPQvMpTR3BeT2jjkYe8rdTCkT91g1sd
J37YgDNuefzrsA+B5/o7
=szjb
-----END PGP SIGNATURE-----
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [email protected]
Automated List Manager                           [email protected]
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to