Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-7341 high CVSS 7.1

Vulnerability in Keycloak (CVE-2024-7341)

Summary

Vulnerability in Keycloak (CVE-2024-7341). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks the current session before authentication to trigger session fixation.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-7341 has been found in Keycloak.
Successful exploitation can lead to full system takeover. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Keycloak CVE-2024-7341" on the vendor's site.

CVE-2024-7341 (Keycloak) — CWE-384 / CVSS v3 7.1
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-384) exists in Keycloak.

📍 Affected scope

Check the vendor advisory for the affected versions of Keycloak.

🔥 Severity

Severity: High (CVSS 7.1/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Keycloak' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Keycloak' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Keycloak を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.keycloak:keycloak-services
[{"type":"ECOSYSTEM","events":[{"introduced":"25.0.0"},{"fixed":"25.0.5"}]}]
Bitnami keycloak
[{"type":"SEMVER","events":[{"introduced":"22.0.0"},{"fixed":"22.0.12"},{"introduced":"24.0.0"},{"fixed":"24.0.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details