{"id":"CVE-2017-8028","published":"2017-11-27T10:00:00Z","modified":"2024-08-05T16:19:29Z","title":"In Pivotal Spring-LDAP versions 1.3.0 - 2.3.1, when connected to some LDAP servers, when no additional attributes are…","vendor":null,"product":null,"tier":"tail","description":{"text":"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.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.02606,"percentile":0.85755,"provenance":"source"},"cwes":[],"references":[{"url":"https://access.redhat.com/errata/RHSA-2018:0319","tags":["vendor-advisory","x_refsource_REDHAT"]},{"url":"https://www.debian.org/security/2017/dsa-4046","tags":["vendor-advisory","x_refsource_DEBIAN"]},{"url":"https://lists.debian.org/debian-lts-announce/2017/11/msg00026.html","tags":["mailing-list","x_refsource_MLIST"]},{"url":"https://www.oracle.com/security-alerts/cpujan2021.html","tags":["x_refsource_MISC"]},{"url":"https://pivotal.io/security/cve-2017-8028","tags":["x_refsource_CONFIRM"]}],"priority":{"score":17.2,"factors":[{"name":"EPSS percentile","points":17.15}]},"affectedVersions":[{"vendor":"n/a","product":"Spring-LDAP Spring-LDAP versions 1.3.0 2.3.1","versions":["Spring-LDAP Spring-LDAP versions 1.3.0 2.3.1"]}],"affected":[{"ecosystem":"Maven","package":"org.springframework.ldap:spring-ldap-core","vulnerableRanges":[">=1.3.0, <2.3.2"],"patched":["2.3.2"],"from":["GHSA-pjqh-2jcc-5j84"],"provenance":"source"}],"summary":{"text":"In Pivotal Spring-LDAP versions 1.3.0 through 2.3.1, the flaw lies in the LDAP BindAuthenticator when it uses DefaultTlsDirContextAuthenticationStrategy with userSearch configured, and the bind does not take effect on some LDAP servers because those vendors require an explicit operation for the bind to apply. An attacker who knows a valid username can authenticate with any password when the server is one of these vendors and no additional attributes are bound.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T21:30:50Z"},"euvd":{"id":"EUVD-2022-4787","exploited":false,"provenance":"source"}}