It was found in Undertow before 1.3.28 that with non-clean TCP close, the Websocket server gets into infinite loop on every IO thread, effectively causing DoS.
The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2017:1411 | vendor advisory |
http://rhn.redhat.com/errata/RHSA-2017-1409.html | vendor advisory |
https://www.debian.org/security/2017/dsa-3906 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2017:3458 | vendor advisory |
https://access.redhat.com/errata/RHSA-2017:1410 | vendor advisory |
https://access.redhat.com/errata/RHSA-2017:1412 | vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2670 | issue tracking vendor advisory |
https://access.redhat.com/errata/RHSA-2017:3455 | vendor advisory |
https://access.redhat.com/errata/RHSA-2017:3456 | vendor advisory |
https://access.redhat.com/errata/RHSA-2017:3454 | vendor advisory |
http://www.securityfocus.com/bid/98965 | vdb entry third party advisory |