dbcve.org
Cloud Pak For SecurityApplication · Ibm

CVE-2023-47728

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-16
Fix available
A fix is available. Upgrade to 1.10.23.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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.22.0 and IBM Cloud Pak for Security 1.10.0.0 through 1.10.11.0 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the request. This information could be used in further attacks against the system. IBM X-Force ID: 272201.

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 and IBM Cloud Pak for Security return detailed technical error messages in HTTP responses, allowing remote attackers to obtain sensitive system information such as stack traces, file paths, and configuration details that could be used for further exploitation.

MitigationConfigure the application to return generic, user-friendly error messages instead of detailed technical stack traces and system information. Disable verbose error handling in production environments.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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 product version
    Locate the installed version of IBM Cloud Pak for Security or IBM QRadar Suite in the system documentation, administrative console, or using the product's version lookup command. Common locations include the admin UI, installation logs, or version API endpoint.
    Affected if The installed 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. Check for verbose error handling configuration
    Access the application configuration settings or administration console and locate error handling, debugging, or verbose error configuration options. Look for settings that control whether detailed stack traces and system information are returned in HTTP error responses.
    Affected if Verbose error handling, debug mode, or detailed error messages are enabled in the configuration.
  3. Test error response behavior
    Send a crafted or malformed request to the application that would trigger an error condition (such as an invalid input, missing parameter, or unexpected request format). Observe the HTTP response for detailed technical information.
    Affected if The HTTP error response contains stack traces, file paths, configuration details, Java/coding errors, or other sensitive system information rather than a generic user-friendly message.
  4. Review application logs for exposed information
    Examine application log files or error logs for instances where detailed technical error messages, stack traces, or system paths were generated and potentially exposed.
    Affected if Logs contain detailed exception stack traces, file paths, or configuration details that would be returned to users in production.

You are affected if your installed version is within the listed ranges AND verbose error handling is enabled, causing detailed system information to appear in HTTP error responses.

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

Configure the application to return generic, user-friendly error messages instead of detailed technical stack traces and system information. Disable verbose error handling in production environments.

Recommended fix High confidence

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

  1. 1. Identify which product is in use: IBM Cloud Pak for Security or IBM QRadar Suite
  2. 2. For Cloud Pak for Security: Schedule maintenance window and upgrade to version 1.10.12.0 or later
  3. 3. For QRadar Suite: Schedule maintenance window and upgrade to version 1.10.23.0 or later
  4. 4. After upgrade, verify that detailed technical error messages are no longer exposed in HTTP responses
  5. 5. Test application functionality to confirm the upgrade did not introduce regressions
Caveat Review IBM release notes for specific version changes as minor/major version differences may include feature or behavior changes

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-2023-47728 — 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-2023-47728 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