Issue summary: The DTLS retransmission logic does not correctly handle
\na handshake message write that is suspended part-way through.
\nThe retransmitted message can be read past the message buffer and
\nthe retransmission overwrites the internal state the suspended write
\nneeds to resume correctly.<\/p>\n
Impact summary: The retransmitted message can disclose a heap memory
\nto the peer as plaintext handshake data or cause a crash and a Denial
\nof Service when the read reaches an unmapped memory region.<\/p>\n
CWE: CWE-125: Out-of-bounds Read<\/p>\n
Description: DTLS handshake messages can be written out in multiple
\nfragments, and a write can suspend mid-message (returning WANT_WRITE)
\nif the underlying transport temporarily cannot accept more data. While
\nsuch a write is suspended, the DTLS retransmission timer may
\nindependently fire and ask the retransmission logic to resend an
\nearlier, already-acknowledged-as-sent message from its retransmit
\nqueue.<\/p>\n
The retransmission logic reused the same internal buffer and position
\ntracking as the message that was still being written, without
\nresetting the position back to the start of the message being
\nretransmitted. As a result the retransmission was read starting from
\nwherever the suspended write had left off, producing a mislabelled
\nmessage whose body was leftover bytes from the other, larger message
\nstill in flight – content that was never meant to be sent at that
\npoint, and which could run past the end of the allocated buffer.<\/p>\n
Separately, even when the retransmission is positioned correctly,
\nallowing it to run to completion while another write is suspended
\noverwrites the same shared bookkeeping that the suspended write
\ndepends on to resume. When the application later resumes the
\nsuspended write (via a subsequent SSL_read(), SSL_write(),
\nSSL_accept(), or SSL_connect() call), it finds that bookkeeping in a
\nstate inconsistent with the message and aborts the process in
\na debugging build.<\/p>\n
The fix resets the retransmission’s read position to the start of the
\nmessage before resending, and skips retransmission entirely whenever a
\nhandshake write is still suspended, deferring to the next call that
\nresumes it instead.<\/p>\n
FIPS impact: no
\nThe affected code is outside the FIPS module boundary.<\/p>\n","protected":false},"excerpt":{"rendered":"
Issue summary: The DTLS retransmission logic does not correctly handle
\na handshake message write that is suspended part-way through.
\nThe retransmitted message can be read past the message buffer and
\nt<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-30632","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/30632","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=30632"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=30632"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=30632"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}