# CVE-2022-2232: Keycloak: ldap injection on username input

> Attackers can inject LDAP queries via username input to bypass authentication or access sensitive data in Keycloak.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 14 Nov 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-8hc5-rmgf-qx6p

## What is CVE-2022-2232?

CVE-2022-2232 is a high-severity vulnerability in Red Hat Single Sign-On 7, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the Keycloak package. This flaw allows an attacker to utilize an LDAP injection to bypass the username lookup or potentially perform other malicious actions.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-2232?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-ldap-federation` | Maven | All versions | 23.0.1 |
| `org.keycloak:keycloak-ldap-federation` | Maven | All versions | 23.0.1 |
| `org.keycloak:keycloak-services` | Maven | All versions | 23.0.1 |
| `org.keycloak:keycloak-services` | Maven | All versions | 23.0.1 |

## How do I fix CVE-2022-2232?

Upgrade org.keycloak:keycloak-ldap-federation to 23.0.1 or later.

## Is CVE-2022-2232 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2232 and fix it if it is affected.

What it is: CVE-2022-2232 is a high-severity vulnerability in Red Hat Single Sign-On 7, published on 14 Nov 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-2022-2232 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-ldap-federation (Maven): affected all versions; fixed in 23.0.1
- org.keycloak:keycloak-ldap-federation (Maven): affected all versions; fixed in 23.0.1
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 23.0.1
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 23.0.1

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-2022-2232/ (Markdown: https://insights.sbomify.com/CVE-2022-2232/index.md)
```

## Sources

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

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