dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2024-25023

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 1.10.23.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 Cloud Pak for Security 1.10.0.0 through 1.10.11.0 and IBM QRadar Suite Software 1.10.12.0 through 1.10.22.0 stores potentially sensitive information in log files that could be read by a local user. IBM X-Force ID: 281429.

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 Cloud Pak for Security and QRadar Suite Software versions store potentially sensitive information in log files that can be read by a local user with access to the system. This information disclosure vulnerability requires local access but could expose sensitive data such as credentials, tokens, or PII that gets written during normal operation.

MitigationUpgrade to IBM Cloud Pak for Security version 1.10.12.0 or later, or QRadar Suite Software version 1.10.23.0 or later. Alternatively, review and restrict access to log file directories, and implement log sanitization to prevent sensitive data from being written.

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.23.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 installed product and version
    Run 'ibmcloud cpfs version' or check the QRadar Suite version via the admin console or command line interface. Look for the exact version number in the output.
    Affected if The version falls within 1.10.0.0 to 1.10.11.0 for Cloud Pak for Security, or 1.10.12.0 to below 1.10.23.0 for QRadar Suite.
  2. Locate log directories
    Find log directories commonly used by the product. Typical paths include /var/log/qradar or /var/log/ibm/cpfs. Check the installation documentation for your specific deployment.
    Affected if Log directories exist and are accessible.
  3. Inspect log files for sensitive content
    Search log files for patterns that may indicate sensitive data: look for strings like 'password', 'token', 'secret', 'api_key', 'Bearer', or base64-encoded strings that resemble credentials.
    Affected if Log files contain any credentials, tokens, API keys, or PII such as usernames, email addresses, or personal identifiers.
  4. Check file permissions on log directories
    Run 'ls -la' on the log directories to verify who has read access. Compare against expected restrictive permissions (should be readable only by privileged users).
    Affected if Log directories or files are readable by non-privileged local users.

You are affected if your installed version is within the vulnerable ranges AND log files contain sensitive information accessible to local users.

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.23.0 or later
Fixed in 1.10.23.0
Interim mitigation

Upgrade to IBM Cloud Pak for Security version 1.10.12.0 or later, or QRadar Suite Software version 1.10.23.0 or later. Alternatively, review and restrict access to log file directories, and implement log sanitization to prevent sensitive data from being written.

Recommended fix Moderate confidence

Cloud Pak for Security: upgrade to >= 1.10.12.0 | QRadar Suite: upgrade to >= 1.10.23.0

  1. 1. Identify your current installation of IBM Cloud Pak for Security or QRadar Suite by running: kubectl get cp4s <instance-name> -n <namespace> or checking the QRadar Suite version in the admin console
  2. 2. For Cloud Pak for Security: Upgrade to version 1.10.12.0 or later (the next release after 1.10.11.0 that contains the security fix)
  3. 3. For QRadar Suite: Upgrade to version 1.10.23.0 or later
  4. 4. After upgrade, verify the fix by reviewing updated log configuration: oc exec -it <pod-name> -n <namespace> -- cat /optibm/si/logging/config/logging.properties
  5. 5. Confirm sensitive data filtering is enabled in the logging configuration by checking for output masking or redaction settings
  6. 6. Test that application functionality remains intact after the version change
Caveat Review IBM Cloud Pak for Security and QRadar Suite release notes for 1.10.12.0+ (Cloud Pak) and 1.10.23.0+ (QRadar) for any deprecated features or migration requirements before upgrading

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

Fix this in Cloud Pak For Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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