Skip to content
Browse files

Fix Use After Free for large message sizes

The buffer to receive messages is initialised to 16k. If a message is
received that is larger than that then the buffer is "realloc'd". This can
cause the location of the underlying buffer to change. Anything that is
referring to the old location will be referring to free'd data. In the
recent commit c1ef7c9 (master) and 4b390b6 (1.1.0) the point in the code
where the message buffer is grown was changed. However s->init_msg was not
updated to point at the new location.


Reviewed-by: Emilia Käsper <>
(cherry picked from commit 0d698f6)
  • Loading branch information
mattcaswell committed Sep 26, 2016
1 parent df7681e commit acacbfa7565c78d2273c0b2a2e5e803f44afefeb
Showing with 17 additions and 3 deletions.
  1. +17 −3 ssl/statem/statem.c
@@ -445,6 +445,21 @@ static void init_read_state_machine(SSL *s)
st->read_state = READ_STATE_HEADER;

static int grow_init_buf(SSL *s, size_t size) {

size_t msg_offset = (char *)s->init_msg - s->init_buf->data;

if (!BUF_MEM_grow_clean(s->init_buf, (int)size))
return 0;

if (size < msg_offset)
return 0;

s->init_msg = s->init_buf->data + msg_offset;

return 1;

* This function implements the sub-state machine when the message flow is in
* MSG_FLOW_READING. The valid sub-states and transitions are:
@@ -545,9 +560,8 @@ static SUB_STATE_RETURN read_state_machine(SSL *s)
/* dtls_get_message already did this */
if (!SSL_IS_DTLS(s)
&& s->s3->tmp.message_size > 0
&& !BUF_MEM_grow_clean(s->init_buf,
&& !grow_init_buf(s, s->s3->tmp.message_size
ssl3_send_alert(s, SSL3_AL_FATAL, SSL_AD_INTERNAL_ERROR);

0 comments on commit acacbfa

Please sign in to comment.