Data exposure via locale-dependent case conversion
Published Dec 4, 2024 · Updated Dec 10, 2024
Improper case handling in Spring LDAP 2.4.3 and earlier and 3.0.0 through 3.2.7 allows remote attackers to read unintended LDAP data. Case-sensitive comparisons use String.toLowerCase() and String.toUpperCase() without locale-stable handling, so exceptional locale conversions can query unintended data. Exploitation requires an affected query path and locale-sensitive input; the reported consequence is limited to data disclosure.
Summary
What happened
Improper case handling in Spring LDAP 2.4.3 and earlier and 3.0.0 through 3.2.7 allows remote attackers to read unintended LDAP data. Case-sensitive comparisons use String.toLowerCase() and String.toUpperCase() without locale-stable handling, so exceptional locale conversions can query unintended data. Exploitation requires an affected query path and locale-sensitive input; the reported consequence is limited to data disclosure.
The record
- CVE
- CVE-2024-38829
- Published
- Dec 4, 2024
- Updated
- Dec 10, 2024
- Vendor
- Spring
- Product
- Spring LDAP
- Classifications
- CWE-178
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2024CVE publishedPublication date reported by the CVE source.
- Dec 10, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.4.0
- Affected versionversion=2.4.0 <=2.4.3
- Affected versionversion=3.0.0 <=3.0.9
- Affected versionversion=3.1.0 <=3.1.7
- Affected versionversion=3.2.0 <=3.2.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo