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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1180-1 | libspring-ldap-java security update |
Debian DSA |
DSA-4046-1 | libspring-ldap-java security update |
EUVD |
EUVD-2022-4787 | 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. |
Github GHSA |
GHSA-pjqh-2jcc-5j84 | Improper Authentication in Pivotal Spring-LDAP |
References
History
No history.
Status: PUBLISHED
Assigner: dell
Published:
Updated: 2024-08-05T16:19:29.484Z
Reserved: 2017-04-21T00:00:00.000Z
Link: CVE-2017-8028
No data.
Status : Deferred
Published: 2017-11-27T10:29:00.720
Modified: 2025-04-20T01:37:25.860
Link: CVE-2017-8028
OpenCVE Enrichment
No data.
Weaknesses
Debian DLA
Debian DSA
EUVD
Github GHSA