Bug 1778265 (CVE-2019-14910)
Summary: | CVE-2019-14910 Keycloak: LDAP authentication accepts invalid passwords when using StartTLS | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Jonathan Christison <jochrist> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | aboyko, chazlett, drieden, krathod, pdrozd, pjindal, security-response-team, sparks, sthorger |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-03 19:04:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1778267 |
Description
Jonathan Christison
2019-11-29 16:43:36 UTC
Acknowledgments: Name: Tero Saarni 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 Statement: This flaw does not affect Red Hat's Single Sign On (RHSSO) product and, thus, no patch will be forthcoming. 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. |