Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-4918

Vulnerability in org.keycloak:keycloak-core (CVE-2023-4918)

Summary

Vulnerability in org.keycloak:keycloak-core (CVE-2023-4918). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 22.0.3 or later.

Original description

The description as published by the source.

A flaw was discovered in Keycloak Core package. When a user registers itself through registration flow, the "password" and "password-confirm" field from the form will occur as regular attributes in the users attributes. The password is also created, but the user attributes must not be there. This way, any entities (all users and clients with proper rights/roles) are able to retrieve the users passwords in clear-text.

Impact

Passwords for self-registered users are stored as cleartext attributes associated with the user.

Mitigation

Disable self-registration for users in all realms until patched.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-2023-4918 has been found in org.keycloak:keycloak-core.
Successful exploitation can lead to full system takeover.
What to do: upgrade org.keycloak:keycloak-core to 22.0.3 or later.
If unsure, ask your IT team or search "org.keycloak:keycloak-core CVE-2023-4918" on the vendor's site.

CVE-2023-4918 (org.keycloak:keycloak-core) — CWE-256
Attack vector: remote (network-reachable) / no user interaction
Patched: 22.0.3 — apply immediately
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-256) exists in org.keycloak:keycloak-core.

📍 Affected scope

Check the vendor advisory for the affected versions of org.keycloak:keycloak-core.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 22.0.3.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.keycloak:keycloak-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.keycloak:keycloak-core to 22.0.3

    ステージング環境で 22.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

Maven org.keycloak:keycloak-core
[{"type":"ECOSYSTEM","events":[{"introduced":"22.0.2"},{"fixed":"22.0.3"}]}]

References

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