Auth bypass in Pivotal Software Spring-Ldap
CVE-2017-8028
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.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.026, 85.6th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Pivotal Software Spring-Ldap — versions 1.3.0, 1.3.1, 1.3.2
- Debian Linux — versions 8.0
- Spring-Ldap Versions 1.3.0 2.3.1 — versions Spring-LDAP Spring-LDAP versions 1.3.0 2.3.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (SarthakShieldersoft/TestVWA). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- RHSA-2018:0319 (vendor-advisory)
- DSA-4046 (vendor-advisory, Third Party Advisory, Issue Tracking)
- [debian-lts-announce] 20171119 [SECURITY] [DLA 1180-1] libspring-ldap-java security update (mailing-list)
- www.oracle.com/security-alerts/cpujan2021.html
- pivotal.io/security/cve-2017-8028 (Issue Tracking, Vendor Advisory)