CVE-2022-2232
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability in Keycloak allows LDAP injection during username lookup operations. An attacker can craft malicious input containing LDAP meta-characters to manipulate LDAP queries, potentially bypassing authentication or executing unauthorized LDAP operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Keycloak is deployedCheck running processes or look for keycloak-related services, WAR files, or container images. Look for keycloak, keycloak-gatekeeper, or Red Hat SSO in process lists, container registries, or deployment manifests.Affected if Keycloak is not present in the environment, the vulnerability does not apply.
-
Check if LDAP user federation is configuredIn the Keycloak admin console, navigate to User Federation. If using LDAP, the provider type will show as 'ldap'. Alternatively, check the keycloak database or realm configuration JSON for 'userFederation' or 'ldap' provider entries.Affected if LDAP federation is not enabled, the LDAP injection flaw cannot be triggered since there is no LDAP query to manipulate.
-
Verify the Keycloak versionCheck the Keycloak server version by examining the JAR, WAR, or container image tags. Common locations: standalone.jar version, pom.xml dependencies, or docker inspect output. Compare against the version that received the CVE-2022-2232 patch.Affected if The installed version predates the patch for CVE-2022-2232 or is an unpatched release.
-
Inspect username lookup configurationIn Keycloak admin console under User Federation > LDAP > Mappers, review any mappers that perform username queries or search operations. Check if the 'username' attribute is used in LDAP search filters without proper escaping.Affected if LDAP mappers exist that use direct user input in search filters without input validation.
The environment is affected only if Keycloak is running with an unpatched version AND has LDAP user federation enabled with search filters that accept user-supplied input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch for CVE-2022-2232 and implement proper input validation/sanitization on all user-supplied fields used in LDAP queries to prevent injection attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2232 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2232 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data