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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2017-8028)

Tobias Schneider discovered that libspring-ldap-java, a Java library for Spring-based applications using the Lightweight Directory Access Protocol, would under some circumstances allow authentication with a correct username but an arbitrary password.

Tobias Schneider discovered that Spring-LDAP would allow authentication with an arbitrary password when the username is correct, no additional attributes are bound and when using LDAP BindAuthenticator with DefaultTlsDirContextAuthenticationStrategy as the authentication strategy and setting userSearch. This occurs because some LDAP vendors require an explicit operation for the LDAP bind to take effect.

For Debian 7 'Wheezy', these problems have been fixed in version 1.3.1.RELEASE-4+deb7u1.

We recommend that you upgrade your libspring-ldap-java packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
417573	SCA: security update for org.springframework.ldap:spring-ldap-core (GHSA-pjqh-2jcc-5j84)	Tenable Cloud Security	SCA Checks	high
417573	SCA: security update for org.springframework.ldap:spring-ldap-core (GHSA-pjqh-2jcc-5j84)	Tenable Self-Hosted Container Security	SCA Checks	high
104752	Debian DSA-4046-1 : libspring-ldap-java - security update	Nessus	Debian Local Security Checks	high
104683	Debian DLA-1180-1 : libspring-ldap-java security update	Nessus	Debian Local Security Checks	high

Detections

Analytics

CVE-2017-8028

high

Tenable Plugins

high

high

high

high