Cyber Resilience

CVE-2023-47728

Info Disclosure in Ibm Cloud Pak For Security 1.10.0.0 – 1.10.11.0

Published
16 August 2024
Modified
21 September 2024
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0046 37th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2023-47728 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Ibm Cloud Pak For Security. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

used in further attacks against the system. IBM X-Force ID: 272201.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-22335Same product: Ibm Cloud Pak For Security
CVE-2023-47727Same product: Ibm Cloud Pak For Security
CVE-2024-28799Same product: Ibm Cloud Pak For Security
CVE-2023-47726Same product: Ibm Cloud Pak For Security
CVE-2025-25020Same product: Ibm Cloud Pak For Security
CVE-2024-25023Same product: Ibm Cloud Pak For Security
CVE-2025-25022Same product: Ibm Cloud Pak For Security
CVE-2024-28782Same product: Ibm Cloud Pak For Security
CVE-2024-25024Same product: Ibm Cloud Pak For Security
CVE-2024-22355Same product: Ibm Cloud Pak For Security

Affected Assets

ibm
cloud pak for security
1.10.0.0 — 1.10.11.0
ibm
qradar suite
1.10.12.0 — 1.10.23.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V16.5.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-209

Detects error messages that leak sensitive information as evidence of disclosure.

addresses: CWE-209

The control directly mitigates generation of error messages containing sensitive authentication details by requiring obscured feedback instead of verbose responses.

addresses: CWE-209

Misdirection allows generation of misleading error messages that withhold or falsify sensitive details.

addresses: CWE-209

Explicitly requires error messages to avoid including sensitive or exploitable details while still supporting corrective action.

addresses: CWE-209

Validation ensures error messages contain only expected, non-sensitive content and blocks leakage via verbose errors.

addresses: CWE-209

Fail-safe procedures can be defined to suppress or sanitize error output, reducing generation of messages that contain sensitive information.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

detects

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match
degrades

Logging policy can require suppression of sensitive data in error messages.

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.

prevents

Application security requirements can specify safe error messaging.

prevents

Secure architecture principles include proper exception handling.

References