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.
References
Link | Resource |
---|---|
http://rhn.redhat.com/errata/RHSA-2017-1409.html | Vendor Advisory |
http://www.securityfocus.com/bid/98965 | Third Party Advisory VDB Entry |
https://access.redhat.com/errata/RHSA-2017:1410 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2017:1411 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2017:1412 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2017:3454 | 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:3458 | Vendor Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2670 | Issue Tracking Vendor Advisory |
https://www.debian.org/security/2017/dsa-3906 | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
AND |
|
History
No history.
Information
Published : 2018-07-27 15:29
Updated : 2024-02-28 16:48
NVD link : CVE-2017-2670
Mitre link : CVE-2017-2670
CVE.ORG link : CVE-2017-2670
JSON object : View
Products Affected
redhat
- jboss_enterprise_application_platform
- enterprise_linux
- undertow
debian
- debian_linux
CWE
CWE-835
Loop with Unreachable Exit Condition ('Infinite Loop')