First published: Wed Nov 08 2017(Updated: )
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.
Credit: security_alert@emc.com security_alert@emc.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pivotal Software Spring-ldap | =1.3.0 | |
Pivotal Software Spring-ldap | =1.3.1 | |
Pivotal Software Spring-ldap | =1.3.1-rc1 | |
Pivotal Software Spring-ldap | =1.3.2 | |
Pivotal Software Spring-ldap | =2.0.0 | |
Pivotal Software Spring-ldap | =2.0.1 | |
Pivotal Software Spring-ldap | =2.0.2 | |
Pivotal Software Spring-ldap | =2.0.3 | |
Pivotal Software Spring-ldap | =2.0.4 | |
Pivotal Software Spring-ldap | =2.1.0 | |
Pivotal Software Spring-ldap | =2.2.0 | |
Pivotal Software Spring-ldap | =2.2.1 | |
Pivotal Software Spring-ldap | =2.3.0 | |
Pivotal Software Spring-ldap | =2.3.1 | |
Debian Debian Linux | =8.0 | |
debian/libspring-ldap-java | ||
redhat/spring-ldap | <2.3.2 | 2.3.2 |
maven/org.springframework.ldap:spring-ldap-core | >=1.3.0<=2.3.1 | 2.3.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.