dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2024-25024

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-15
Fix available
A fix is available. Upgrade to 1.10.24.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
IBM QRadar Suite Software 1.10.12.0 through 1.10.23.0 and IBM Cloud Pak for Security 1.10.0.0 through 1.10.11.0 stores user credentials in plain clear text which can be read by a local user. IBM X-Force ID: 281430.

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

IBM QRadar Suite Software (versions 1.10.12.0-1.10.23.0) and IBM Cloud Pak for Security (versions 1.10.0.0-1.10.11.0) store user credentials in plaintext, allowing any local user with system access to read sensitive authentication credentials directly from storage.

MitigationApply vendor-supplied patches to upgrade QRadar Suite Software beyond 1.10.23.0 and Cloud Pak for Security beyond 1.10.11.0; rotate all potentially exposed credentials as a precautionary measure.

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
Cloud Pak For SecurityApplication
Affected:>= 1.10.0.0, <= 1.10.11.0
Qradar SuiteApplication
Affected:>= 1.10.12.0, < 1.10.24.0

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
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 checks

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

  1. Identify the installed IBM QRadar Suite Software version
    Use the product's built-in version reporting tool or check the /opt/ibm directory for version manifests. Run: find /opt -name 'version*' -o -name 'release*' 2>/dev/null and examine the output for the 1.10.x version string.
    Affected if The installed version is between 1.10.12.0 and 1.10.23.0 inclusive, or less than 1.10.24.0.
  2. Identify the installed IBM Cloud Pak for Security version
    Access the Cloud Pak for Security administration console or use the oc command line tool to query the operator version: oc get csv -A | grep ibm-cp-security.
    Affected if The installed version is between 1.10.0.0 and 1.10.11.0 inclusive.
  3. Locate credential storage locations
    Search for configuration or credential files within the product's data directories. Common paths include /data, /config, or /opt directories under the product installation root.
    Affected if Credential configuration files exist in the product directories and are readable by local system users.
  4. Verify file permissions on credential storage
    Run ls -la on identified credential storage paths to check read permissions for non-privileged users.
    Affected if Files containing credentials are readable by users other than the application service account (world-readable or group-readable).
  5. Inspect credential files for plaintext content
    Examine identified credential files using cat or strings to determine if passwords, API keys, or authentication tokens are stored without encryption.
    Affected if Credentials appear in plaintext (readable base64, plain text, or unencrypted format) within storage files.

A user is affected if their installed QRadar Suite version is 1.10.12.0 through 1.10.23.0, or Cloud Pak for Security version is 1.10.0.0 through 1.10.11.0, AND local users can read credential storage files without elevation.

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.10.24.0 or later
Fixed in 1.10.24.0
Interim mitigation

Apply vendor-supplied patches to upgrade QRadar Suite Software beyond 1.10.23.0 and Cloud Pak for Security beyond 1.10.11.0; rotate all potentially exposed credentials as a precautionary measure.

Recommended fix Moderate confidence

IBM QRadar Suite 1.10.24.0 or later; IBM Cloud Pak for Security version beyond 1.10.11.0

  1. 1. Back up all current configuration and user data before initiating the upgrade.
  2. 2. Review IBM Cloud Pak for Security and QRadar Suite upgrade documentation for your specific deployment model.
  3. 3. Upgrade IBM QRadar Suite from any version < 1.10.24.0 to version 1.10.24.0 or later.
  4. 4. If using IBM Cloud Pak for Security, upgrade from version 1.10.0.0-1.10.11.0 to a version beyond 1.10.11.0 that contains the security fix.
  5. 5. After upgrade, verify that credential storage has been updated to use encrypted or hashed formats rather than plaintext.
  6. 6. Test authentication workflows to ensure the upgrade did not disrupt user login functionality.
Caveat Review IBM release notes for breaking changes between your current version and 1.10.24.0; some configuration or integration changes may be required

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

Fix this in Cloud Pak For Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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