CVE-2017-8028: High severity pivotal software spring ldap vulnerability
In Pivotal Spring-LDAP versions 1.3.0 - 2.3.1, when connected to some LDAP servers, when no additional attributes are bound, and when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and setting userSearch, authentication is allowed with an arbitrary password when the username is correct. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.
Other sources
When connected to some LDAP servers, when no additional attributes are bound, and when using LDAP BindAuthenticator with org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy as the authentication strategy, and setting userSearch, authentication is allowed with an arbitrary password when the username is correct. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.
References:
https://pivotal.io/security/cve-2017-8028
Upstream issue:
https://github.com/spring-projects/spring-ldap/issues/430
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-8028?
CVE-2017-8028 is classified as a moderate severity vulnerability.
How do I fix CVE-2017-8028?
To resolve CVE-2017-8028, upgrade to Pivotal Spring-LDAP version 2.3.2 or later.
Which software versions are affected by CVE-2017-8028?
CVE-2017-8028 affects Pivotal Spring-LDAP versions 1.3.0 to 2.3.1.
What is the main issue with CVE-2017-8028?
The main issue with CVE-2017-8028 is that it allows for improper authentication against certain LDAP servers.
What authentication strategy is involved in CVE-2017-8028?
CVE-2017-8028 involves the LDAP BindAuthenticator using org.springframework.ldap.core.support.DefaultTlsDirContextAuthenticationStrategy.