dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2024-12799

CRITICAL · 10.0 CVSS v4.0 Published 2025-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Insufficiently Protected Credentials vulnerability in OpenText Identity Manager Advanced Edition on Windows, Linux, 64 bit allows Privilege Abuse. This vulnerability could allow an authenticated user to obtain higher privileged user’s sensitive information via crafted payload. This issue affects Identity Manager Advanced Edition: from 4.8.0.0 through 4.8.7.0102, 4.9.0.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 · high confidence

Authenticated privilege abuse vulnerability in OpenText Identity Manager allows a lower-privileged user to obtain higher-privileged user's sensitive credential information through a crafted payload. The vulnerability stems from insufficient protection of credentials in storage or transmission within the identity management system.

MitigationUpgrade to OpenText Identity Manager version beyond 4.8.7.0102 and 4.9.0.0. As an authenticated attack, enforce least-privilege access controls and monitor for anomalous credential access patterns until patched.

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
Network
Complexity
Low
Privileges
None
Authentication
Y
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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:Y/R:U/V:C/RE:H/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 the installed OpenText Identity Manager version
    Check the product's About page, version file, or run: im Version or a similar command-line tool provided by the installation. Alternatively, inspect the installer logs or the product's registry/manifest files for the exact build number.
    Affected if The installed version is 4.8.7.0102 or below, or 4.9.0.0 or below, indicating it is a vulnerable release.
  2. Confirm the user is authenticated within the Identity Manager system
    Verify that the target user account exists in the OpenText Identity Manager user directory and has authenticated successfully at least once. This vulnerability requires an authenticated session.
    Affected if A valid user account with lower privileges exists in the system, which could be exploited to access higher-privileged credential data.
  3. Review credential storage encryption settings
    Inspect the Identity Manager configuration files (such as config.xml, imanager.properties, or similar) for encryption settings related to credential storage. Look for parameters governing how passwords and sensitive credentials are stored in the backend database or directory.
    Affected if Credential encryption is disabled, weakly configured, or uses outdated algorithms, making the stored credential data accessible through the vulnerability.
  4. Examine the credential transmission configuration
    Check whether TLS or other encryption is enforced for credential transmission between the Identity Manager components. Review the server configuration and network transport settings for credential-related operations.
    Affected if Credential transmission is unencrypted or uses fallback protocols that do not protect the payload from interception or manipulation.
  5. Audit credential access logs for anomalous patterns
    Review OpenText Identity Manager audit and access logs for events where lower-privileged users accessed credential data or performed operations outside their typical scope. Look for the specific API endpoint or feature used to retrieve other users' credentials.
    Affected if Logs show credential access by users without sufficient privileges, indicating the vulnerability may have been exploited in the environment.

A user is affected if OpenText Identity Manager version is 4.8.7.0102 or below (or 4.9.0.0 and below) and the system stores or transmits credentials without adequate protection, allowing an authenticated low-privilege user to access higher-privileged credential information.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to OpenText Identity Manager version beyond 4.8.7.0102 and 4.9.0.0. As an authenticated attack, enforce least-privilege access controls and monitor for anomalous credential access patterns until patched.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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