Homepage

Improper Authentication Affecting libspring-ldap-java package, versions <1.3.1.RELEASE-5+deb8u1

Severity

 Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.44% (62nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Authentication vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIAN8-LIBSPRINGLDAPJAVA-264429
  • published27 Nov 2017
  • disclosed27 Nov 2017
Report a new vulnerability Found a mistake?

Introduced: 27 Nov 2017

CVE-2017-8028  (opens in a new tab)
CWE-287  (opens in a new tab)

How to fix?

Upgrade Debian:8 libspring-ldap-java to version 1.3.1.RELEASE-5+deb8u1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libspring-ldap-java package and not the libspring-ldap-java package as distributed by Debian. See How to fix? for Debian:8 relevant fixed versions and status.

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.