CVE-2021-22532 is a high severity (CVSS 7.6) possible denial of service in the NLDAP component of OpenText (formerly NetIQ) eDirectory. The NVD record says versions before 9.2.4.0000 are affected, and the vendor release notes list the fix in eDirectory 9.2 SP5. Upgrade to 9.2 SP5 or later.
What's affected
- OpenText eDirectory before 9.2.4.0000, per the NVD record.
- The eDirectory 9.2 SP5 release notes (August 2021) say that release resolves CVE-2021-22532 and CVE-2021-22533.
- Source conflict: the record states the range as before 9.2.4.0000, while the vendor places the fix in 9.2 SP5. If you run 9.2 SP4, do not assume you are clear. Confirm with the vendor, and plan to reach SP5 or later.
- The impact is mostly availability, with limited confidentiality and integrity effects. A low privilege account is required.
- KEV status: false.
How to check if you're exposed
Check the eDirectory version on each server.
Use iManager or the version tools described in the vendor documentation to read the installed version, then compare it with 9.2 SP5. Also note which servers expose LDAP to wider networks, since the NLDAP service is the component involved.
What to do now
- Identify every eDirectory server and its version, including replicas.
- Upgrade to eDirectory 9.2 SP5 or later following the vendor upgrade guide, one replica at a time.
- Limit which networks can reach LDAP and LDAPS ports to the systems that need them.
- Review resource limits and monitoring for NLDAP, so you can see unusual connection or request volume.
- Also apply the fix for CVE-2021-22533 in the same upgrade, since SP5 covers both.
Why it matters
The class is CWE-770, allocation of resources without limits or throttling. A directory server is shared infrastructure for login and access decisions, so any condition that lets an authenticated user consume more than a fair share of it can slow or stop many applications at once.
Directory outages are expensive because everything that authenticates against them is affected. A medium looking availability bug can still cause a wide incident, so treat a directory upgrade as a planned change with a rollback plan, not as a routine patch.
If you run a multi server tree, upgrade replicas in a planned order and confirm replication health between steps. A patch that is applied unevenly can leave you with servers on different versions for longer than you intended, so write down which server is on which version and when each one moves.
Quick check
Which release fixes this?
The vendor release notes for eDirectory 9.2 SP5 say it resolves this CVE and CVE-2021-22533.
The record says before 9.2.4.0000. Is 9.2 SP4 safe?
Do not assume so. The vendor places the fix in SP5, and the two statements differ. Confirm with the vendor and upgrade to SP5 or later.
Sources
Last reviewed: 19 October 2026.