# CVE-2020-35518: Information disclosure in 389-ds-base > An unauthenticated attacker can determine if specific LDAP entries exist by observing differences in authentication replies. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Mar 2021 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2020-35518, GHSA-vg4h-9m5m-rchq, OESA-2022-1602, OESA-2022-2056, RHSA-2021:0599, RHSA-2021:1086, RHSA-2021:1243, RHSA-2021:1258, RHSA-2021:2323, SUSE-SU-2021:0724-1, UBUNTU-CVE-2020-35518, openSUSE-SU-2021:0418-1 ## What is CVE-2020-35518? CVE-2020-35518 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 26 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-203 (Observable Discrepancy), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2020-35518? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `389-ds-base` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-debuginfo` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-debugsource` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-devel` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-legacy-tools` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-legacy-tools-debuginfo` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-libs` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-libs-debuginfo` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-snmp` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base-snmp-debuginfo` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `cockpit-389-ds` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `python3-lib389` | Red Hat:directory_server:11.1::el8 | All versions | 0:1.4.2.12-5.module+el8dsrv+9896+eb95346c | | `389-ds-base` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-debuginfo` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-debugsource` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-devel` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-legacy-tools` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-legacy-tools-debuginfo` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-libs` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-libs-debuginfo` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-snmp` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base-snmp-debuginfo` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `cockpit-389-ds` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `python3-lib389` | Red Hat:directory_server:11.2::el8 | All versions | 0:1.4.3.21-3.module+el8dsrv+10401+3d549418 | | `389-ds-base` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:7::client | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base-snmp` | Red Hat:enterprise_linux:7::server | All versions | 0:1.3.10.2-12.el7_9 | | `389-ds-base` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.3.10.2-12.el7_9 | Products: Redhat 389 Directory Server, Redhat Directory Server, Redhat Enterprise Linux. ## How do I fix CVE-2020-35518? Apply the vendor's patch. ## Is CVE-2020-35518 being exploited? There is no known exploitation of CVE-2020-35518 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Enterprise Linux - [CVE-2026-11770](https://insights.sbomify.com/CVE-2026-11770/): 389-ds-base: 389-ds-base: pre-auth ldap filter injection in cleanallruv status check (high 7.5) - [CVE-2026-15722](https://insights.sbomify.com/CVE-2026-15722/): Memory corruption in Red Hat Directory Server 11.5 E4S for RHEL 8 (high 7.5) - [CVE-2026-9064](https://insights.sbomify.com/CVE-2026-9064/): Denial of service in Red Hat Directory Server 11.5 E4S for RHEL 8 (high 7.5) - [CVE-2010-2222](https://insights.sbomify.com/CVE-2010-2222/): Null dereference in Red Hat Directory Server (high 7.5) - [CVE-2026-11611](https://insights.sbomify.com/CVE-2026-11611/): 389-ds-base: 389-ds-base: content sync plugin unbounded queue growth and race conditions (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-35518 and fix it if it is affected. What it is: CVE-2020-35518 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 26 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-35518 in the wild and no public exploit code. Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-35518/ (Markdown: https://insights.sbomify.com/CVE-2020-35518/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-35518 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-35518 - OSV: https://osv.dev/vulnerability/CVE-2020-35518 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-35518/ Summaries are generated and may contain mistakes; the official description above is the record.