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.
References
Link | Resource |
---|---|
https://pivotal.io/security/cve-2017-8028 | Issue Tracking Vendor Advisory |
https://www.debian.org/security/2017/dsa-4046 | Issue Tracking Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2017/11/msg00026.html | |
https://access.redhat.com/errata/RHSA-2018:0319 | |
https://www.oracle.com/security-alerts/cpujan2021.html |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Information
Published : 2017-11-27 02:29
Updated : 2021-01-20 07:15
NVD link : CVE-2017-8028
Mitre link : CVE-2017-8028
JSON object : View
CWE
CWE-287
Improper Authentication
Products Affected
debian
- debian_linux
pivotal_software
- spring-ldap