It was reported that HTTPS NIO connector uses no timeout when reading SSL handshake from a client to tie up a thread on the server just by creating a socket. Attacker could create socket and then never sends the handshake or any data at all, which causes the thread to remain occupied indefinitely so long as the socket remains open. Product bug: https://bugzilla.redhat.com/show_bug.cgi?id=1307039
Undertow in EAP 7 is not vulnerable. The SSL handshake read does not occupy a thread with Undertow and the handshake read times out as expected by the listener's read-timeout.
This issue has been addressed in the following products: JBEAP 6.4.z for RHEL 6 Via RHSA-2016:0598 https://rhn.redhat.com/errata/RHSA-2016-0598.html
This issue has been addressed in the following products: JBEAP 6.4.z for RHEL 7 Via RHSA-2016:0597 https://rhn.redhat.com/errata/RHSA-2016-0597.html
This issue has been addressed in the following products: JBEAP 6.4.z for RHEL 6 Via RHSA-2016:0596 https://rhn.redhat.com/errata/RHSA-2016-0596.html
This issue has been addressed in the following products: JBEAP 6.4.z for RHEL 5 Via RHSA-2016:0595 https://rhn.redhat.com/errata/RHSA-2016-0595.html
This issue has been addressed in the following products: Via RHSA-2016:0599 https://rhn.redhat.com/errata/RHSA-2016-0599.html