First published: Wed Oct 04 2023(Updated: )
A flaw was found in Undertow. When an AJP request is sent that exceeds the max-header-size attribute in ajp-listener, JBoss EAP is marked in an error state by mod_cluster in httpd, causing JBoss EAP to close the TCP connection without returning an AJP response. This happens because mod_proxy_cluster marks the JBoss EAP instance as an error worker when the TCP connection is closed from the backend after sending the AJP request without receiving an AJP response, and stops forwarding. This issue could allow a malicious user could to repeatedly send requests that exceed the max-header-size, causing a Denial of Service (DoS).
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
JBoss Enterprise Application Platform | ||
JBoss Enterprise Application Platform | =7.0.0 | |
Red Hat Single Sign-On | =7.0 | |
Red Hat Undertow |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-5379 has been rated as a moderate severity vulnerability.
To fix CVE-2023-5379, ensure that your JBoss EAP and Undertow installations are updated to the latest version that addresses this issue.
CVE-2023-5379 affects Red Hat JBoss Enterprise Application Platform, Red Hat Single Sign-On, and Red Hat Undertow.
CVE-2023-5379 can cause JBoss EAP to enter an error state and close TCP connections without responding to AJP requests.
CVE-2023-5379 was reported in 2023 and is associated with the Undertow server in JBoss EAP.