CVE-2020-35518Network attack vector

Unauthenticated directory-entry enumeration via bind-response details

Published Mar 26, 2021 · Updated Aug 4, 2024

Information disclosure in affected 389 Directory Server releases allows remote attackers to enumerate LDAP entries through bind requests. The send_ldap_result_ext path reads additional result text from the wrong pblock key, causing failed binds for nonexistent DNs to include "No such entry" while existing DNs return only invalid credentials. No authentication is required; repeated guesses reveal which directory DNs exist but do not expose attribute values or permit changes.

CVSS severity5.3
Medium
EPSS probability1.54%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in affected 389 Directory Server releases allows remote attackers to enumerate LDAP entries through bind requests. The send_ldap_result_ext path reads additional result text from the wrong pblock key, causing failed binds for nonexistent DNs to include "No such entry" while existing DNs return only invalid credentials. No authentication is required; repeated guesses reveal which directory DNs exist but do not expose attribute values or permit changes.

The record

CVE
CVE-2020-35518
Published
Mar 26, 2021
Updated
Aug 4, 2024
Vendor
389 Directory Server
Product
389 Directory Server
Classifications
CWE-200, CWE-203, T1087.002
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 26, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 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.

  1. Affected versionversion=389-ds-base 2.0.3, 389-ds-base 1.4.4.13, 389-ds-base 1.4.3.19

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

389 Directory Server · 389 Directory Serverversion=389-ds-base 2.0.3, 389-ds-base 1.4.4.13, 389-ds-base 1.4.3.19

Published CVSS scores

5.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
5.0NIST NVDAV:N/AC:L/Au:N/C:P/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
CWE-203Observable Discrepancy
T1087.002Domain Account

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