Safeguard
Vulnerability Analysis•

CVE-2021-22533: Medium Sensitive Data in eDirectory Logs

CVE-2021-22533 is sensitive information written to log files in OpenText eDirectory 9.2.4.0000. The fix is in 9.2 SP5, so upgrade and review old logs.

Safeguard Security Team
3 min read

CVE-2021-22533 is a medium severity (CVSS 6.5) flaw where OpenText (formerly NetIQ) eDirectory 9.2.4.0000 writes sensitive information into a log file. The vendor release notes say eDirectory 9.2 SP5 resolves it. Upgrade, then review and protect logs written by the affected version.

What's affected

  • OpenText eDirectory 9.2.4.0000, per the NVD record.
  • The eDirectory 9.2 SP5 release notes (August 2021) list CVE-2021-22533 as resolved, along with CVE-2021-22532.
  • The record requires a high privilege account and rates confidentiality and integrity impact as high.
  • Neither source states exactly what data is logged, so we do not describe it here. Check the vendor notes for specifics.
  • KEV status: false.

How to check if you're exposed

Confirm the eDirectory version on each server.

Use iManager or the version tools described in the vendor documentation to read the installed version. Then locate where eDirectory writes its logs and who can read them. Log files that hold sensitive data are exposed to everyone with file access, backup access or log collection access.

What to do now

  1. Upgrade to eDirectory 9.2 SP5 or later.
  2. Restrict read access to eDirectory log directories to the administrators who need it.
  3. Review where logs are copied, such as backups, log shippers and support bundles, and apply the same access rules there.
  4. Rotate any credentials you find in old log files, once you have confirmed what the logs contain.
  5. Set a retention limit so that old logs from the affected version are removed.

Why it matters

The class is CWE-532, insertion of sensitive information into a log file. Logs are written for troubleshooting and are often treated as low risk, but they tend to be copied widely: into backups, ticket attachments and central log platforms. Anything sensitive that lands in them spreads with them.

Fixing the software stops new entries. It does not clean up old ones. After the upgrade, the cleanup of existing logs and their copies is the part most teams forget, and it is often the part that matters most.

It also helps to ask a wider question after any logging flaw: which other products write detailed logs that your teams copy around? A short review of log contents and log access across your directory, identity and application tiers often finds similar exposure before it becomes a finding. Keep the review short and repeat it when you upgrade major versions.

Quick check

Does upgrading remove the sensitive data already logged?

No. The upgrade changes future behavior. You still need to find and protect or remove older logs and their copies.

Which version fixes it?

The vendor release notes list eDirectory 9.2 SP5 as resolving this CVE.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.