Keycloak: LDAP authentication accepts invalid passwords when using StartTLS
Published Dec 5, 2019
9.8
CRITICALCVSS 3.1
EPSS 1.05%
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.
Affected products
- Vendor n/a Product Keycloak Defaultn/a
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||
|---|---|---|---|---|---|---|
| n/a | Keycloak | n/a |
|
No data.
Red Hat Single Sign-On 7
rh-sso7-keycloak
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Single Sign-On 7 | rh-sso7-keycloak | Not affected | n/a |
No package ranges for this CVE.
Remediation
Red Hat statement
This flaw does not affect Red Hat's Single Sign On (RHSSO) product and, thus, no patch will be forthcoming.
Red Hat mitigation
Disabling STARTTLS will fix the authentication flaw but leave the connection to the LDAP server unencrypted. Utilizing LDAPS will add a layer of encryption back to the LDAP connection but only at the SSLv3 level which also poses problems in and of itself.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
AV:N/AC:L/Au:N/C:P/I:P/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 3, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Table of values (12 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 3, 2026 | 1.05% (0.01054) | 63.20th | v5 (v2026.06.15) |
| Sep 20, 2026 | 1.05% (0.01054) | 62.90th | v5 (v2026.06.15) |
| Jul 20, 2024 | 0.18% (0.00182) | 55.92th | v3 (v2023.03.01) |
| Jun 22, 2024 | 0.18% (0.00182) | 55.71th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.18% (0.00182) | 53.70th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.89% (0.00885) | 27.89th | v2 (v2022.01.01) |
| Apr 1, 2022 | 0.89% (0.00885) | 24.24th | v2 (v2022.01.01) |
| Feb 4, 2022 | 9.03% (0.09029) | 86.86th | v2 (v2022.01.01) |
| Feb 3, 2022 | 1.84% (0.01840) | 47.83th | v1 |
| Jan 6, 2022 | 1.84% (0.01840) | 47.32th | v1 |
| Jan 5, 2022 | 0.42% (0.00416) | 26.65th | v5 (v2026.06.15) |
| Apr 14, 2021 | 0.42% (0.00416) | 0.00th | v1 |
References (7)
- https://access.redhat.com/security/cve/CVE-2019-14910 Vendor Advisory
- https://access.redhat.com/security/cve/cve-2019-14910
- https://bugzilla.redhat.com/show_bug.cgi?id=1778265 Issue Tracking
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14910 x_refsource_CONFIRMIssue TrackingMitigationVendor Advisory
- https://github.com/advisories/GHSA-jf86-9434-f8c2 Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2019-14910
- https://www.cve.org/CVERecord?id=CVE-2019-14910
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2019-14910 | Vendor Advisory | |
| https://access.redhat.com/security/cve/cve-2019-14910 | ||
| https://bugzilla.redhat.com/show_bug.cgi?id=1778265 | Issue Tracking | |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14910 | x_refsource_CONFIRMIssue TrackingMitigationVendor Advisory | |
| https://github.com/advisories/GHSA-jf86-9434-f8c2 | Advisory | |
| https://nvd.nist.gov/vuln/detail/CVE-2019-14910 | ||
| https://www.cve.org/CVERecord?id=CVE-2019-14910 |
Change history (0)
No recorded changes yet.