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.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| redhat | 389_directory_server | 1.4.3.19 | - |
| redhat | 389_directory_server | 1.4.4.0 - 1.4.4.13 | - |
| redhat | 389_directory_server |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
6
Affected Products
8
References
redhat / 389_directory_server
| 2.0.0 - 2.0.3 |
| - |
| redhat | directory_server | - | - |
| redhat | enterprise_linux | - | - |
| redhat | enterprise_linux | - | - |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Exploitability
Impact