Undertow vulnerabilities
We track 4 vulnerabilities in Undertow products. 4 are rated high or critical, and none are known to be exploited. The most recent was published on February 23, 2023.
Latest Undertow vulnerabilities
- 7.5 High severity
undertow: Server-Side Request Forgery
The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS client protocol.
- 7.5 High severity
undertow: Unchecked Return Value
A flaw was found in Undertow. For an AJP 400 response, EAP 7 is improperly sending two response packets, and those packets have the reuse flag set even though JBoss EAP closes the connection. A failure occurs when the connection is reused after a 400 by CPING
- 7.5 High severity
undertow: Uncontrolled Resource Consumption
A flaw was found in Undertow. A potential security issue in flow control handling by the browser over HTTP/2 may cause overhead or a denial of service in the server. This flaw exists because of an incomplete fix for CVE-2021-3629.
- 7.5 High severity
Undertow: Uncontrolled Resource Consumption
When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy. This behavior results in that a front