dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2024-11604

HIGH · 7.3 CVSS v4.0 Published 2026-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
No privileges

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
Insertion of Sensitive Information into Log File vulnerability in the SCIM Driver module in OpenText IDM Driver and Extensions on Windows, Linux, 64 bit allows authenticated local users to obtain sensitive information via access to log files. This issue affects IDM SCIM Driver: 1.0.0.0000 through 1.0.1.0300 and 1.1.0.0000.

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 · high confidence

The SCIM Driver module in OpenText IDM Driver and Extensions writes sensitive information (potentially credentials, tokens, or user PII) to log files. Authenticated local users with file system access can read these logs to obtain sensitive data that should not be exposed.

MitigationRestrict file system permissions on IDM SCIM Driver log directories to prevent unauthorized access. Update to a patched version when available. Review and sanitize any sensitive data before logging.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
High
Authentication
None
User interaction
A
Scope
P

CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:N/R:U/V:C/RE:M/U:Red

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 OpenText IDM Driver installation
    Search for IDM Driver installation directories or check installed programs list for 'OpenText IDM Driver' or 'IDM Driver and Extensions'
    Affected if OpenText IDM Driver is installed on the system
  2. Verify SCIM Driver module status
    Check if the SCIM Driver module is loaded or enabled within the IDM Driver configuration. Look for SCIM-related configuration files or service entries.
    Affected if The SCIM Driver module is installed and enabled
  3. Locate SCIM Driver log directories
    Search for log directories related to IDM or SCIM. Common paths include installation directories with 'logs' subfolders, or check IDM configuration for custom log paths.
    Affected if Log directories exist and are accessible
  4. Inspect log file permissions
    Use file system tools (ls -la on Linux, icacls or Properties > Security on Windows) to check who has read access to the SCIM Driver log files and directories.
    Affected if Log files are readable by users other than the IDM service account or administrators
  5. Scan logs for sensitive data patterns
    Open log files and search for patterns indicating credentials, tokens, passwords, or PII (e.g., look for 'password', 'token', 'secret', 'credential', or base64-encoded strings in user-related entries).
    Affected if Log files contain plaintext or easily decoded credentials, tokens, or user PII

A system is affected if OpenText IDM Driver with the SCIM Driver module is installed, log files are accessible to non-privileged local users, and those logs contain sensitive information such as credentials, tokens, or user PII.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict file system permissions on IDM SCIM Driver log directories to prevent unauthorized access. Update to a patched version when available. Review and sanitize any sensitive data before logging.

Recommended fix Moderate confidence

IDM SCIM Driver version greater than 1.1.0.0000 (contact OpenText/NetIQ support for the exact latest fixed version)

  1. Identify the currently installed IDM SCIM Driver version by checking the driver's version property or installed files
  2. Navigate to the OpenText/NetIQ product download portal or support site
  3. Download the latest IDM SCIM Driver version that is newer than 1.1.0.0000
  4. Review the release notes for the new version to confirm the CVE-2024-11604 vulnerability is addressed
  5. Before installation, backup the current driver configuration and any custom settings
  6. Install the upgraded SCIM Driver version following the standard upgrade procedure documented in the IDM installation guide
  7. After upgrade, verify that sensitive information is no longer being written to log files by reviewing new log entries
  8. Ensure log files have appropriate file permissions restricted to authorized administrators only
Caveat Review OpenText upgrade documentation for any configuration changes required between version 1.1 and the new version, as default settings or behavior may have changed

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11604 — 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-2024-11604 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