CVE-2024-11734

6.5 MEDIUM

📋 TL;DR

A denial-of-service vulnerability in Keycloak allows administrative users with realm settings modification privileges to disrupt service by injecting newlines into security headers. This causes the server to write to already-terminated requests, leading to request failures. Only authenticated administrative users with specific permissions are affected.

💻 Affected Systems

Products:
  • Keycloak
Versions: Keycloak versions before 24.0.10, 25.0.6, and 26.0.0
Operating Systems: All platforms running Keycloak
Default Config Vulnerable: ⚠️ Yes
Notes: Requires administrative user with 'manage-realm' or equivalent permissions to modify realm settings.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Administrative user causes complete service disruption, making Keycloak unavailable for authentication and authorization services.

🟠

Likely Case

Targeted DoS attacks against specific realms or services, causing intermittent authentication failures.

🟢

If Mitigated

Limited impact with proper administrative access controls and monitoring in place.

🌐 Internet-Facing: MEDIUM - Internet-facing Keycloak instances are vulnerable if administrative interfaces are exposed.
🏢 Internal Only: HIGH - Internal administrative users pose significant risk due to their privileged access.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated administrative access and knowledge of the vulnerability.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Keycloak 24.0.10, 25.0.6, or 26.0.0

Vendor Advisory: https://access.redhat.com/security/cve/CVE-2024-11734

Restart Required: Yes

Instructions:

1. Backup Keycloak configuration and database. 2. Download and install patched version (24.0.10, 25.0.6, or 26.0.0). 3. Restart Keycloak service. 4. Verify service functionality.

🔧 Temporary Workarounds

Restrict Administrative Access

all

Limit administrative user permissions and implement principle of least privilege.

Input Validation Proxy

all

Deploy WAF or reverse proxy to filter newline characters in security headers.

🧯 If You Can't Patch

  • Implement strict administrative access controls and monitor for unusual realm setting changes.
  • Deploy network segmentation to isolate Keycloak administrative interfaces from regular users.

🔍 How to Verify

Check if Vulnerable:

Check Keycloak version via admin console or by examining server logs for version information.

Check Version:

Check Keycloak server logs or use: java -jar keycloak-admin-cli.jar --version

Verify Fix Applied:

Verify installed version is 24.0.10, 25.0.6, or 26.0.0 or higher, and test administrative functions.

📡 Detection & Monitoring

Log Indicators:

  • Unusual realm setting modifications
  • Multiple failed requests from administrative users
  • Error logs mentioning terminated requests

Network Indicators:

  • Unusual patterns in administrative API calls
  • Spikes in failed authentication requests

SIEM Query:

source="keycloak" AND ("realm settings modified" OR "security headers" OR "request terminated")

🔗 References

📤 Share & Export