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.
Remediation
References
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
Related Vulnerabilities
CVE-2022-36907 Vulnerability in maven package org.jenkins-ci.plugins:openshift-deployer
CVE-2022-25167 Vulnerability in maven package org.apache.flume.flume-ng-sources:flume-jms-source
CVE-2022-37257 Vulnerability in npm package steal
CVE-2023-37951 Vulnerability in maven package com.mabl.integration.jenkins:mabl-integration
CVE-2022-40151 Vulnerability in maven package com.thoughtworks.xstream:xstream