Improper Authentication Affecting spring-ldap-core package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 IDSNYK-RHEL10-SPRINGLDAPCORE-16695834
- published15 May 2026
- disclosed16 Oct 2017
Introduced: 16 Oct 2017
CVE-2017-8028 (opens in a new tab)How to fix?
There is no fixed version for RHEL:10 spring-ldap-core.
NVD Description
Note: Versions mentioned in the description apply only to the upstream spring-ldap-core package and not the spring-ldap-core package as distributed by RHEL.
See How to fix? for RHEL:10 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.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=1510968
- https://access.redhat.com/security/cve/CVE-2017-8028
- https://access.redhat.com/errata/RHSA-2018:0319
- https://lists.debian.org/debian-lts-announce/2017/11/msg00026.html
- https://pivotal.io/security/cve-2017-8028
- https://www.debian.org/security/2017/dsa-4046
- https://www.oracle.com/security-alerts/cpujan2021.html