high8.1
CVE-2017-8028
Improper Authentication in Pivotal Spring-LDAP
Impact
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.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| maven | org.springframework.ldap:spring-ldap-core | >= 1.3.0, <= 2.3.1 | 2.3.2 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Pivotal Software | Spring-Ldap | Versions 1.3.0, 1.3.1, 1.3.2, 2.0.0, 2.0.1, 2.0.2 |
| Debian | Debian Linux | Version 8.0 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://access.redhat.com/errata/RHSA-2018:0319
- https://lists.debian.org/debian-lts-announce/2017/11/msg00026.html
- https://pivotal.io/security/cve-2017-8028
- https://www.debian.org/security/2017/dsa-4046
- https://www.oracle.com/security-alerts/cpujan2021.html
- https://github.com/advisories/GHSA-pjqh-2jcc-5j84
- https://nvd.nist.gov/vuln/detail/CVE-2017-8028
- https://github.com/spring-projects/spring-ldap/commit/08e8ae289bbd1b581986c7238604a147119c1336