Bug 1778265 (CVE-2019-14910) - CVE-2019-14910 Keycloak: LDAP authentication accepts invalid passwords when using StartTLS
Summary: CVE-2019-14910 Keycloak: LDAP authentication accepts invalid passwords when u...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2019-14910
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1778267
TreeView+ depends on / blocked
 
Reported: 2019-11-29 16:43 UTC by Jonathan Christison
Modified: 2021-02-16 20:57 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in keycloak 7.x where an invalid password is accepted for user authentication when LDAP user federation and STARTTLS is used instead of SSL/TLS from the LDAP server. This can allow an attacker to log into a system using any entry for a password authentication and still gain access to the system.
Clone Of:
Environment:
Last Closed: 2019-12-03 19:04:59 UTC
Embargoed:

Attachments (Terms of Use)

Description Jonathan Christison 2019-11-29 16:43:36 UTC 
When using Keycloak LDAP user federation with StartTLS any password, valid or invalid will be accepted

Mitigation: 
* If possible use SSL (ldaps) instead
* Disable StartTLS
Comment 3 Paramvir jindal 2019-12-02 10:02:00 UTC 
Acknowledgments:

Name: Tero Saarni
Comment 6 Product Security DevOps Team 2019-12-03 19:04:59 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2019-14910
Comment 10 Eric Christensen 2019-12-06 13:28:02 UTC 
Statement:

This flaw does not affect Red Hat's Single Sign On (RHSSO) product and, thus, no patch will be forthcoming.
Comment 11 Eric Christensen 2019-12-06 13:28:04 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.