First published: Wed Oct 04 2023(Updated: )
When an AJP request is sent that exceeds the max-header-size attribute in ajp-listener, JBoss EAP is marked as an error state by mod_cluster in httpd. The problem is that requests exceeding the max-header-size cause JBoss EAP to close the TCP connection without returning an AJP response. A malicious user could exploit this behavior by repeatedly sending requests that exceed the max-header-size, it causes a denial-of-service attack. This is because mod_proxy_cluster marks JBoss 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.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat JBoss Enterprise Application Platform |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2242099 is classified as high due to the potential for service disruption and denial of service.
To fix REDHAT-BUG-2242099, increase the max-header-size attribute in the ajp-listener configuration to accommodate larger requests.
The issue in REDHAT-BUG-2242099 is caused by AJP requests exceeding the configured max-header-size, which leads to JBoss EAP closing the TCP connection.
Yes, REDHAT-BUG-2242099 is exploitable as it may allow attackers to disrupt services by sending oversized AJP requests.
REDHAT-BUG-2242099 affects Red Hat JBoss EAP across multiple versions that utilize the misconfigured ajp-listener.