# CVE-2023-6484: Keycloak: log injection during webauthn authentication or registration

> Attackers can inject text into logs during WebAuthn authentication, compromising log integrity in Keycloak deployments.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2024
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-j628-q885-8gr5

## What is CVE-2023-6484?

CVE-2023-6484 is a medium-severity vulnerability in Red Hat RHEL-8 based Middleware Containers, published on 25 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2023-6484?

4 open source packages ship an affected version, including org.keycloak:keycloak-services.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions | 22.0.9 |
| `org.keycloak:keycloak-services` | Maven | All versions | 22.0.9 |
| `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 23.0.5 |
| `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 23.0.5 |

## How do I fix CVE-2023-6484?

Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 22.0.9 or 23.0.5.

## Is CVE-2023-6484 being exploited?

There is no known exploitation of CVE-2023-6484 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6484 and fix it if it is affected.

What it is: CVE-2023-6484 is a medium-severity vulnerability in Red Hat RHEL-8 based Middleware Containers, published on 25 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6484 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.9
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.9
- org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 23.0.5
- org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 23.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6484/ (Markdown: https://insights.sbomify.com/CVE-2023-6484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6484
- OSV: https://osv.dev/vulnerability/CVE-2023-6484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6484/
Summaries are generated and may contain mistakes; the official description above is the record.