# CVE-2019-14910: Keycloak Authentication Error

> Attackers can bypass authentication and gain unauthorized access when Keycloak uses LDAP with StartTLS instead of LDAPS.

- **Severity:** Critical 9.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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:** No
- **Published:** 5 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jf86-9434-f8c2

## What is CVE-2019-14910?

CVE-2019-14910 is a critical authentication bypass vulnerability in Redhat Keycloak, published on 5 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS from the LDAP server (ldaps), in this case user authentication succeeds even if invalid password has entered.

Weakness: CWE-295 (Improper Certificate Validation), CWE-592 (DEPRECATED: Authentication Bypass Issues), CWE-305 (Authentication Bypass by Primary Weakness), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-14910?

2 open source packages ship an affected version, including org.keycloak:keycloak-parent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-parent` | Maven | From 7.0.0 to 7.0.1 | None |
| `org.keycloak:keycloak-parent` | Maven | From 7.0.0 to 7.0.1 | None |

Products: Redhat Keycloak.

## How do I fix CVE-2019-14910?

No fix has been published for CVE-2019-14910 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-14910 being exploited?

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

## Other vulnerabilities in Redhat Keycloak

- [CVE-2022-4361](https://insights.sbomify.com/CVE-2022-4361/): Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC (critical 10.0)
- [CVE-2022-1245](https://insights.sbomify.com/CVE-2022-1245/): Keycloak vulnerable to privilege escalation on Token Exchange feature (critical 9.8)
- [CVE-2021-20195](https://insights.sbomify.com/CVE-2021-20195/): keycloak Self Stored Cross-site Scripting vulnerability (critical 9.6)
- [CVE-2019-14909](https://insights.sbomify.com/CVE-2019-14909/): Keycloak Authentication Error (critical 9.3)
- [CVE-2022-3782](https://insights.sbomify.com/CVE-2022-3782/): Keycloak vulnerable to path traversal via double URL encoding (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14910 and fix it if it is affected.

What it is: CVE-2019-14910 is a critical authentication bypass vulnerability in Redhat Keycloak, published on 5 Dec 2019. 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-2019-14910 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-parent (Maven): affected from 7.0.0 up to 7.0.1; no fix listed
- org.keycloak:keycloak-parent (Maven): affected from 7.0.0 up to 7.0.1; no fix listed

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

## Sources

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

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