Safeguard
Vulnerability Analysis•

CVE-2022-26322: Medium Log Exposure in Identity Manager REST Driver

CVE-2022-26322 logs sensitive data in OpenText Identity Manager REST Driver before 1.1.2.0200. Apply patch 1.1.2.0300 and review old logs now.

Safeguard Security Team
3 min read

CVE-2022-26322 is a medium severity flaw in the OpenText (NetIQ) Identity Manager REST Driver that inserts sensitive information into a log file, scored 4.9. NVD says versions before 1.1.2.0200 are affected, while the 1.1.2.0300 readme lists the security fix, so apply 1.1.2.0300 and review logs.

What's affected

The NVD record says the OpenText Identity Manager REST Driver is affected in versions before 1.1.2.0200. The vendor readme I could read is for patch 1.1.2.0300. It lists Security Fix CVE-2022-26322 under that release and lists a set of ordinary fixes under the previous release, 1.1.2.0200.

Those two statements disagree on which build contains the fix. The safe reading is to install 1.1.2.0300 or later, and to ask OpenText support if you run exactly 1.1.2.0200. The readme says the update applies to REST drivers running Identity Manager 4.8.x or later and changes the driver version to 1.1.2.0300 once applied.

NVD scores the flaw 4.9 Medium with a network vector and high privileges required, and a confidentiality impact only. That fits a flaw in which sensitive values are written to logs that administrators can read.

The advisory text I read does not say what data is logged, so I will not guess. The record's kev flag is false.

Weakness class per the record: CWE-532.

How to check if you're exposed

Check the installed driver version. The readme says the version changes to 1.1.2.0300 after the patch, and the Linux package is netiq-DXMLRESTDrv:

rpm -q netiq-DXMLRESTDrv

On Windows installs, compare the dates and sizes of RESTCommon.jar, RESTDriverShim.jar and RESTUtil.jar in the driver folder with the ones in the patch download.

Next, check where the driver writes logs and who can read them. Exposure from this flaw is about log content, so the more people and systems that can read the trace or log files, the larger the exposure.

What to do now

  1. Confirm the REST driver version on each Identity Manager server and remote loader.
  2. Back up the current driver configuration, then apply patch 1.1.2.0300 following the readme steps for your platform.
  3. Restart eDirectory or the Remote Loader instance as the readme instructs, and then restart the driver.
  4. Review old driver logs and trace files for sensitive values, restrict access to them, and rotate any credentials that appear.

Why it matters

The weakness is insertion of sensitive information into a log file (CWE-532). Logs are written for troubleshooting, then copied to central log stores, shared with support and kept for months. Anything sensitive that lands there lives much longer and is visible to more people than the system that produced it.

For an identity management driver the sensitive data could include provisioning details or secrets that move between systems. The record does not say which, so the safe assumption is that anything the driver handles could be affected.

The fix stops the logging going forward. It does not clean old logs, which is why log review and credential rotation are part of the response.

Quick check

Does patching clean up old logs?

No. The patch changes what the driver logs from then on. Existing log files may still hold sensitive values, so review and protect them.

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.