dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2024-22335

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

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

IBM QRadar Suite and IBM Cloud Pak for Security versions store potentially sensitive information in log files that can be read by a local user with system access. This information disclosure vulnerability stems from improper handling of sensitive data in logging mechanisms.

MitigationReview and restrict log file permissions to authorized administrators only, implement log sanitization to prevent sensitive data from being written to logs, and apply IBM security patches for the affected versions.

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.18.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 IBM product and version
    Run 'ibmcpd --version' for Cloud Pak for Security or check the QRadar Suite version via the admin console or command line interface
    Affected if The version falls within 1.10.0.0-1.10.11.0 for Cloud Pak for Security or 1.10.12.0 to below 1.10.18.0 for QRadar Suite
  2. Locate application log files
    Find log directories for the IBM product - typically under the installation root in 'logs' or 'var/log' subdirectories
    Affected if Log files exist in standard product directories and contain application output
  3. Inspect log file permissions
    Use 'ls -la' on identified log directories and files to check read permissions for non-privileged users
    Affected if Log files are readable by users other than the root or dedicated application user
  4. Search logs for sensitive data patterns
    Grep through log files for patterns indicating credentials, tokens, or PII (search for keywords like 'password', 'token', 'secret', or base64-encoded strings in log contents)
    Affected if Sensitive data such as passwords, API tokens, or user credentials appear in plain text within log files

A system is affected if it runs IBM Cloud Pak for Security version 1.10.0.0-1.10.11.0 or IBM QRadar Suite version 1.10.12.0-1.10.17.x and has log files containing sensitive data readable by non-privileged 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.18.0 or later
Fixed in 1.10.18.0
Interim mitigation

Review and restrict log file permissions to authorized administrators only, implement log sanitization to prevent sensitive data from being written to logs, and apply IBM security patches for the affected versions.

Recommended fix High confidence

Cloud Pak for Security: 1.10.12.0+ | QRadar Suite: 1.10.18.0+

  1. Identify the currently installed IBM QRadar Suite or Cloud Pak for Security version using the system management console or version command
  2. For Cloud Pak for Security: Upgrade to version 1.10.12.0 or later
  3. For QRadar Suite: Upgrade to version 1.10.18.0 or later
  4. After upgrade, verify the new version is running and review IBM's release notes for any additional post-upgrade configuration requirements
  5. Review log files created after the upgrade to confirm sensitive information is no longer being written

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

Fix this in Cloud Pak For Security Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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