dbcve.org
Cloud Pak SystemApplication · Ibm

CVE-2023-38013

HIGH · 7.5 CVSS v3.1 Published 2025-01-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Cloud Pak System 2.3.3.0, 2.3.3.3, 2.3.3.3 iFix1, 2.3.3.4, 2.3.3.5, 2.3.3.6, 2.3.3.6 iFix1, 2.3.3.6 iFix2, 2.3.3.7, and 2.3.3.7 iFix1 could disclose sensitive information in HTTP responses that could aid in further attacks against the system.

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 Cloud Pak System versions 2.3.3.0 through 2.3.3.7 iFix1 contains an information disclosure vulnerability where sensitive information is exposed in HTTP responses. This could reveal system details, credentials, or configuration data that aids attackers in planning further attacks against the system.

MitigationApply IBM-provided patches or upgrade to a patched version of IBM Cloud Pak System. Review HTTP response headers and bodies to identify and remediate any sensitive data exposure.

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 SystemApplication
Affected:= 2.3.3.0= 2.3.3.3= 2.3.3.4= 2.3.3.5= 2.3.3.6= 2.3.3.7

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed IBM Cloud Pak System version
    Access the IBM Cloud Pak System admin console or use the system management interface to view the current version. Alternatively, check the version through the command line interface if available: 'cpd-cli manage --version' or consult system documentation for version retrieval commands.
    Affected if The installed version is 2.3.3.0, 2.3.3.3, 2.3.3.4, 2.3.3.5, 2.3.3.6, or 2.3.3.7.
  2. Confirm the specific iFix level
    Check if the installation has any interim fixes (iFix) applied. Review the patch level through the IBM Cloud Pak System management portal or by examining the installed fix list via the system console.
    Affected if The system is at version 2.3.3.7 without iFix2 or later patches applied.
  3. Identify exposed HTTP response data
    Capture and review HTTP responses from the IBM Cloud Pak System web interfaces and APIs. Use a web proxy or browser developer tools to inspect response headers and bodies for any sensitive system details, credentials, configuration data, or internal paths.
    Affected if HTTP responses contain sensitive information such as system paths, credentials, internal IP addresses, or configuration details that should not be exposed to end users.
  4. Review authentication-protected endpoints
    Test HTTP responses from both authenticated and unauthenticated endpoints. Compare responses before and after login to identify any information leakage in error messages, headers, or debug output.
    Affected if Any HTTP response reveals information that could aid an attacker in planning further attacks, such as software version details, internal network structure, or session tokens.

A user is affected if their IBM Cloud Pak System version matches 2.3.3.0 through 2.3.3.7 iFix1 and HTTP responses are found to contain sensitive system information.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM-provided patches or upgrade to a patched version of IBM Cloud Pak System. Review HTTP response headers and bodies to identify and remediate any sensitive data exposure.

Recommended fix Moderate confidence
  1. Contact IBM support to obtain the security patch for CVE-2023-38013
  2. Request the specific fixed version (2.3.3.8 or later) from IBM based on your support entitlement
  3. Apply the patch following IBM's standard Cloud Pak System patch deployment procedures
  4. After patching, verify that sensitive information is no longer disclosed in HTTP responses

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

Fix this in Cloud Pak System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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