Fix memory leak from zero-length DTLS fragments.
authorAdam Langley <agl@imperialviolet.org>
Fri, 6 Jun 2014 21:30:33 +0000 (14:30 -0700)
committerMatt Caswell <matt@openssl.org>
Wed, 6 Aug 2014 19:41:23 +0000 (20:41 +0100)
commit8ca4c4b25e050b881f3aad7017052842b888722d
tree7918c4c1481382b5f446b8564ea3a553b8f65a66
parent0598468fc04fb0cf2438c4ee635b587aac1bcce6
Fix memory leak from zero-length DTLS fragments.

The |pqueue_insert| function can fail if one attempts to insert a
duplicate sequence number. When handling a fragment of an out of
sequence message, |dtls1_process_out_of_seq_message| would not call
|dtls1_reassemble_fragment| if the fragment's length was zero. It would
then allocate a fresh fragment and attempt to insert it, but ignore the
return value, leaking the fragment.

This allows an attacker to exhaust the memory of a DTLS peer.

Fixes CVE-2014-3507

Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Emilia Käsper <emilia@openssl.org>
ssl/d1_both.c