dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2024-22336

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: 279976.

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 contain a vulnerability where potentially sensitive information is written to log files. A local user with access to the system could read these log files and obtain the sensitive data, resulting in information disclosure.

MitigationUpgrade to IBM QRadar Suite 1.10.18.0 or later, and IBM Cloud Pak for Security 1.10.12.0 or later. Alternatively, restrict local user access to log directories and review log configurations to ensure sensitive data is not 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.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. Determine installed version of IBM QRadar Suite
    Run 'version' command or check /opt/ibm/qradar/webconsole/sensor/version file, or use the QRadar admin console UI under Help > About
    Affected if version is >= 1.10.12.0 and < 1.10.18.0
  2. Determine installed version of IBM Cloud Pak for Security
    Check the operator deployment version via 'oc get csv -n <namespace>' or use 'cpctl utils --get-version' from the utility container
    Affected if version is >= 1.10.0.0 and <= 1.10.11.0
  3. Locate log files in the QRadar or Cloud Pak for Security environment
    Check standard log directories: /var/log/qradar, /var/log/ibm/cloudpak, or paths referenced in the application's log4j or logging configuration files
    Affected if log files exist and are readable by local users beyond the intended administrator audience
  4. Inspect log contents for sensitive data patterns
    Search log files for keywords such as 'password', 'token', 'secret', 'api_key', 'credential', 'Authorization', 'Bearer', or other authentication-related strings using 'grep -i -E' commands
    Affected if any of these logs contain plaintext or weakly obfuscated sensitive credentials, tokens, or authentication headers

A user is affected if they run an installed version within the affected ranges AND their log files contain sensitive information accessible to local users with limited privileges.

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

Upgrade to IBM QRadar Suite 1.10.18.0 or later, and IBM Cloud Pak for Security 1.10.12.0 or later. Alternatively, restrict local user access to log directories and review log configurations to ensure sensitive data is not being written.

Recommended fix High confidence

QRadar Suite 1.10.18.0 or later (Cloud Pak for Security customers should migrate to QRadar Suite)

  1. For QRadar Suite: Upgrade to version 1.10.18.0 or later which contains the fix for this vulnerability.
  2. For Cloud Pak for Security: IBM Cloud Pak for Security reached End of Support as of 30 April 2024. Migrate to IBM QRadar Suite 1.10.18.0 or later, which is the successor product.
  3. After upgrading, verify that log files no longer contain sensitive information by reviewing log configurations and auditing log contents.
  4. Implement log rotation and access controls to limit exposure of any potentially sensitive data in logs.
Caveat Cloud Pak for Security is end-of-life; customers must migrate to QRadar Suite. QRadar Suite upgrades may require compatibility checks with existing integrations.

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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-22336 — 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-22336 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