CVE-2023-6484VulnerabilityPublished 25 Apr 2024Updated 21 Nov 2025

CVE-2023-6484: keycloak · Log Injection

Affects keycloakSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.0% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.keycloak/keycloak`pkg:maven/org.keycloak/keycloak`Other threats	Affected =0 =23.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2023-6484, European organizations should: 1) Monitor Keycloak vendor communications closely and apply security patches or updates as soon as they become available to address this vulnerability. 2) Implement input validation and sanitization on all authentication form inputs, particularly for WebAuthn parameters, to prevent injection of malicious text into logs. 3) Enhance logging infrastructure by using log management solutions that support log integrity verification and anomaly detection to identify suspicious log entries indicative of injection attempts. 4) Restrict access to authentication endpoints to trusted networks or users where feasible, reducing exposure to unauthenticated injection attempts. 5) Conduct regular security audits and penetration testing focusing on authentication workflows and logging mechanisms. 6) Educate security and operations teams about the risks of log injection and the importance of verifying log integrity during incident investigations. 7) Consider deploying Web Application Firewalls (WAFs) or similar controls to detect and block injection patterns targeting authentication forms. These measures collectively reduce the likelihood and impact of log injection attacks stemming from this vulnerability.

Description

A log injection flaw was found in Keycloak. A text string may be injected through the authentication form when using the WebAuthn authentication mode. This issue may have a minor impact to the logs integrity.

Impact

For European organizations, the primary impact of CVE-2023-6484 is on the integrity of security logs generated by Keycloak during WebAuthn authentication. Compromised logs can mislead security teams, obscure evidence of attacks, or facilitate evasion by threat actors. This undermines trust in audit trails and complicates incident detection and response. While the vulnerability does not directly expose sensitive data or disrupt services, the degradation of log integrity can have downstream effects on compliance with regulations such as GDPR, which mandate accurate logging for security and accountability. Organizations in sectors with stringent audit requirements, such as finance, healthcare, and government, may face increased risk. Additionally, Keycloak is often deployed in cloud and hybrid environments, so the vulnerability could affect a broad range of infrastructures. The absence of known exploits reduces immediate risk, but the ease of injection without authentication means attackers could exploit this flaw opportunistically, especially in environments exposed to untrusted users or external authentication attempts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Nov 2025, 07:01 UTC

Technical details

References

Community reviews

Related threats