CVE-2024-28799
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 · uneditedIBM 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 displays sensitive data improperly to a local privileged user, in non default configurations, during back-end commands which may result in the unexpected disclosure of this information. IBM X-Force ID: 287173.
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 confidenceIBM QRadar Suite Software (1.10.12.0-1.10.23.0) and IBM Cloud Pak for Security (1.10.0.0-1.10.11.0) improperly expose sensitive data to local privileged users during back-end command execution in non-default configurations, allowing unauthorized information disclosure.
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>= 1.10.0.0, <= 1.10.11.0>= 1.10.12.0, <= 1.10.23.0CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product and versionRun the product's version command or check the installed package version. For QRadar Suite, use 'qradar --version' or check the RPM/package version. For Cloud Pak for Security, check the operator or container image version.Affected if The installed version falls within 1.10.12.0-1.10.23.0 for QRadar Suite or 1.10.0.0-1.10.11.0 for Cloud Pak for Security.
-
Confirm product typeDetermine whether the environment is running IBM QRadar Suite Software or IBM Cloud Pak for Security, as both are affected but in different version ranges.Affected if The product is either IBM QRadar Suite Software or IBM Cloud Pak for Security within the specified version ranges.
-
Review non-default configurationsAudit configuration files and settings related to back-end command execution. Check for any custom or non-standard configurations that may have been applied beyond default settings. Look for configuration parameters that control command execution privilege levels or data exposure.Affected if Non-default configurations exist that alter how back-end commands execute or how their output is handled.
-
Assess local privileged user accessReview which local users have elevated or privileged access to the system. Check group memberships and sudo configurations that grant privileged access to system resources.Affected if Local privileged users exist who could potentially access sensitive data during back-end command execution.
You are affected if you run IBM QRadar Suite (1.10.12.0-1.10.23.0) or IBM Cloud Pak for Security (1.10.0.0-1.10.11.0) with non-default configurations that allow local privileged users to access sensitive data during back-end command execution.
Generated from the published advisory. Verify against your own configuration.
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 · scopedReview and remediate non-default configurations that may expose sensitive data during backend command execution. Limit local privileged user access and apply available IBM patches for affected versions.
Cloud Pak for Security: migrate to QRadar Suite 1.10.24.0 or later; QRadar Suite: 1.10.24.0 or later
- 1. Identify the current installed version of IBM QRadar Suite or Cloud Pak for Security
- 2. For Cloud Pak for Security (versions 1.10.0.0-1.10.11.0): Upgrade to version 1.10.12.0 or later (or migrate to QRadar Suite as Cloud Pak for Security is end-of-life)
- 3. For QRadar Suite (versions 1.10.12.0-1.10.23.0): Upgrade to version 1.10.24.0 or later
- 4. Review IBM Cloud Pak for Security end-of-life announcements as the product is being retired
- 5. After upgrade, verify the non-default configuration settings that triggered this vulnerability have been addressed
- 6. Test that sensitive data is no longer disclosed during back-end commands for local privileged users
- 7. Consult IBM Security Bulletin for complete remediation details
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-28799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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