A vulnerability was found in the Keycloak Server. The Keycloak Server is vulnerable to a denial of service (DoS) attack due to improper handling of proxy headers. When Keycloak is configured to accept incoming proxy headers, it may accept non-IP values, such as obfuscated identifiers, without proper validation. This issue can lead to costly DNS resolution operations, which an attacker could exploit to tie up IO threads and potentially cause a denial of service. The attacker must have access to send requests to a Keycloak instance that is configured to accept proxy headers, specifically when reverse proxies do not overwrite incoming headers, and Keycloak is configured to trust these headers.
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
| Link | Tags |
|---|---|
| https://access.redhat.com/errata/RHSA-2024:10175 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2024:10176 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2024:10177 | vendor advisory |
| https://access.redhat.com/errata/RHSA-2024:10178 | vendor advisory |
| https://access.redhat.com/security/cve/CVE-2024-9666 | vdb entry |
| https://bugzilla.redhat.com/show_bug.cgi?id=2317440 | issue tracking |