Vulnerabilities · 2020 · Redhat
CVE-2020-35518
Redhat 389 Directory Server vulnerability
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.
Affected products
389 Directory Server, Directory Server, Enterprise Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Redhat 389 Directory Server runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- bugzilla.redhat.com/show_bug.cgi?id=1905565 · Patch
- github.com/389ds/389-ds-base/commit/b6aae4d8e7c8a6ddd21646f94fef1bf7f22c3f32 · Patch
- github.com/389ds/389-ds-base/commit/cc0f69283abc082488824702dae485b8eae938bc · Patch
- github.com/389ds/389-ds-base/issues/4480 · Patch
- nvd.nist.gov/vuln/detail/CVE-2020-35518
- cve.org/CVERecord?id=CVE-2020-35518
More vulnerabilities in Redhat products
CVE-2025-53862CVE-2025-53861CVE-2025-47711CVE-2025-46400CVE-2025-46399CVE-2025-46398CVE-2025-46397CVE-2025-35036All 5,277
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.