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.
CPE | Name | Operator | Version |
---|---|---|---|
org.springframework.ldap:spring-ldap-core | ge | 1.3.0 | |
org.springframework.ldap:spring-ldap-core | le | 2.3.1 |
access.redhat.com/errata/RHSA-2018:0319
github.com/advisories/GHSA-pjqh-2jcc-5j84
github.com/spring-projects/spring-ldap/commit/08e8ae289bbd1b581986c7238604a147119c1336
lists.debian.org/debian-lts-announce/2017/11/msg00026.html
nvd.nist.gov/vuln/detail/CVE-2017-8028
pivotal.io/security/cve-2017-8028
www.debian.org/security/2017/dsa-4046
www.oracle.com/security-alerts/cpujan2021.html