Skip to content

Improper Authentication in Pivotal Spring-LDAP

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Apr 5, 2024

Package

maven org.springframework.ldap:spring-ldap-core (Maven)

Affected versions

>= 1.3.0, <= 2.3.1

Patched versions

2.3.2

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.

References

Published by the National Vulnerability Database Nov 27, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jun 30, 2022
Last updated Apr 5, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.426%
(75th percentile)

Weaknesses

CVE ID

CVE-2017-8028

GHSA ID

GHSA-pjqh-2jcc-5j84

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.