dbcve.org
Identity Manager Rest DriverApplication · Netiq

CVE-2022-26322

HIGH · 7.5 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 1.1.2.0200 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Possible Insertion of Sensitive Information into Log File Vulnerability in Identity Manager has been discovered in OpenText™ Identity Manager REST Driver. This impact version before 1.1.2.0200.

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 confidence

A vulnerability in OpenText Identity Manager REST Driver versions before 1.1.2.0200 allows sensitive information to be inserted into log files. This log injection vulnerability could expose credentials, tokens, or other confidential data that gets written to application logs, potentially leading to unauthorized access if those logs are compromised.

MitigationUpgrade the Identity Manager REST Driver to version 1.1.2.0200 or later. Additionally, audit existing log files for any exposed sensitive data and implement log sanitization to prevent sensitive parameters from being recorded.

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
Identity Manager Rest DriverApplication
Affected:< 1.1.2.0200

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Identity Manager REST Driver is installed
    Check for the presence of the NetIQ/Identity Manager REST Driver components on the system. Look for REST Driver installation directories or check the Identity Manager driver list via the Identity Manager Administrator or console.
    Affected if The REST Driver is not installed - the vulnerability only applies if this specific driver is present.
  2. Determine the installed REST Driver version
    Locate the REST Driver version information. This is typically found in the driver configuration, about dialog, or version file within the REST Driver installation directory. Compare the version number to the affected threshold of 1.1.2.0200.
    Affected if The installed version is lower than 1.1.2.0200 - versions below this threshold are vulnerable.
  3. Verify logging is enabled for the REST Driver
    Check the REST Driver configuration to determine if logging is turned on. Review the driver parameters or configuration files for log level settings that control whether events are written to log files.
    Affected if Logging is enabled - the vulnerability only exposes data when logging is active and the driver writes events to log files.
  4. Locate and examine REST Driver log files
    Access the log files generated by the REST Driver. Search within these logs for patterns that may indicate exposed credentials, tokens, authorization headers, passwords, or other sensitive parameters that should not be recorded.
    Affected if Log files contain sensitive data such as credentials, tokens, or authentication headers - this confirms the vulnerability has been triggered.

A system is affected if the Identity Manager REST Driver is installed with a version lower than 1.1.2.0200 and logging is enabled, potentially exposing sensitive data in log files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.1.2.0200 or later
Fixed in 1.1.2.0200
Interim mitigation

Upgrade the Identity Manager REST Driver to version 1.1.2.0200 or later. Additionally, audit existing log files for any exposed sensitive data and implement log sanitization to prevent sensitive parameters from being recorded.

Recommended fix Moderate confidence

1.1.2.0200

  1. Check current Identity Manager Rest Driver version to confirm it is below 1.1.2.0200
  2. Obtain Identity Manager Rest Driver version 1.1.2.0200 or later from OpenText/NetIQ
  3. Follow OpenText/NetIQ standard upgrade procedures to install the fixed version
  4. Verify the new version is running (1.1.2.0200 or later)
  5. Review log configurations to ensure sensitive information is no longer being written to log files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Identity Manager Rest Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26322 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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