Description
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.
Metrics
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | Spring-LDAP Spring-LDAP versions 1.3.0 2.3.1 | Spring-LDAP Spring-LDAP versions 1.3.0 2.3.1 |
References
- 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-8028Issue Tracking, Vendor Advisory
- https://www.debian.org/security/2017/dsa-4046Issue Tracking, Third Party Advisory
- https://www.oracle.com/security-alerts/cpujan2021.html
- 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-8028Issue Tracking, Vendor Advisory
- https://www.debian.org/security/2017/dsa-4046Issue Tracking, Third Party Advisory
- https://www.oracle.com/security-alerts/cpujan2021.html
Timeline
- Published
- Nov 27, 2017
- Last modified
- Jun 17, 2026
- NVD status
- Modified