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.
Product
[UNKNOWN] undertow vulnerabilities
3 published CVES affecting [UNKNOWN] undertow, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 3
- Critical
- 0
- High
- 1
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest [UNKNOWN] undertow CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 3.6%
-
MediumCVSS 6.5 EPSS 3.1%
It was discovered in Undertow that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response....
-
MediumCVSS 6.1 EPSS 1.8%
In Undertow before versions 7.1.2.CR1, 7.1.2.GA it was found that the fix for CVE-2016-4993 was incomplete and Undertow web server is vulnerable to the injection of arbitrary HTTP headers, and also response splitting, due to insufficient sanitization and validation of user input...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.