spring-ldap: Authentication with userSearch and STARTTLS allows authentication with arbitrary password
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | Spring-LDAP Spring-LDAP versions 1.3.0 2.3.1 | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat JBoss A-MQ 6.3 | |||
| Camel | cpe:/a:redhat:jboss_amq:6.3 | RHSA-2018:0319 | 2018-02-14T00:00:00Z |
| Red Hat JBoss Fuse 6.3 | |||
| Camel | cpe:/a:redhat:jboss_fuse:6.3 | RHSA-2018:0319 | 2018-02-14T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1180-1 | libspring-ldap-java security update |
Debian DSA |
DSA-4046-1 | libspring-ldap-java security update |
EUVD |
EUVD-2022-4787 | 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. |
Github GHSA |
GHSA-pjqh-2jcc-5j84 | Improper Authentication in Pivotal Spring-LDAP |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 2.6% (2.606% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.