CVE-2021-22518
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability identified in OpenText™ Identity Manager AzureAD Driver that allows logging of sensitive information into log file. This impacts all versions before 5.1.4.0
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe OpenText Identity Manager AzureAD Driver before version 5.1.4.0 has a vulnerability that causes sensitive information to be written to log files, potentially exposing credentials, tokens, PII, or other confidential data that could be accessed by attackers with log file access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.1.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify AzureAD Driver versionLocate the Identity Manager driver configuration files or driver metadata. Check the driver version property in the driver configuration, about dialog, or installation manifest. Compare the found version to 5.1.4.0.Affected if The installed version is lower than 5.1.4.0
-
Locate log directoryFind the directory where the Identity Manager AzureAD Driver writes its log files. This is typically configured in the driver parameters or global logging settings.Affected if Log files exist and the driver version is below 5.1.4.0
-
Inspect log files for sensitive dataSearch log files for patterns that may indicate exposed credentials, authentication tokens, or PII (look for keywords like 'password', 'token', 'secret', 'key', or base64-encoded strings that resemble credentials).Affected if Log files contain visible plaintext credentials, tokens, or other sensitive information that should not have been logged
-
Review historical log filesCheck for any archived or older log files that may predate an upgrade to version 5.1.4.0 or later.Affected if Historical log files exist from versions prior to 5.1.4.0 and contain sensitive data
A user is affected if the OpenText Identity Manager AzureAD Driver installed in their environment is version 5.1.4.0 or earlier, or if historical log files from vulnerable versions containing sensitive information are present.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.1.4.0
Upgrade to OpenText Identity Manager AzureAD Driver version 5.1.4.0 or later to remediate the vulnerability, and audit/secure or remove existing historical log files that may contain sensitive information from unpatched versions.
5.1.4.0
- Obtain Identity Manager AzureAD Driver version 5.1.4.0 or later from OpenText/NETIQ support portal or official distribution channels
- Backup current driver configuration and settings
- Install or apply the updated driver package following standard deployment procedures
- After upgrade, review log configuration to confirm sensitive information is no longer being written to log files
- Verify the driver is functioning correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22518 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22518 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data