When binding against a DN during authentication, the reply from 389-ds-base will be different whether the DN exists or not. This can be used by an unauthenticated attacker to check the existence of an entry in the LDAP database.
References
| Link | Resource |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=1905565 | Issue Tracking Patch Vendor Advisory |
| https://github.com/389ds/389-ds-base/issues/4480 | Patch Third Party Advisory |
| https://github.com/389ds/389-ds-base/commit/cc0f69283abc082488824702dae485b8eae938bc | Patch Third Party Advisory |
| https://github.com/389ds/389-ds-base/commit/b6aae4d8e7c8a6ddd21646f94fef1bf7f22c3f32 | Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Information
Published : 2021-03-26 10:15
Updated : 2022-08-05 10:42
NVD link : CVE-2020-35518
Mitre link : CVE-2020-35518
JSON object : View
CWE
CWE-203
Observable Discrepancy
Products Affected
redhat
- 389_directory_server
- enterprise_linux
- directory_server


