dbcve.org
Cloud Pak SystemApplication · Ibm

CVE-2023-38714

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 about the system 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 that could expose sensitive system details. The specific attack vector and exposed information type are not detailed in the available documentation, but the CVSS 7.5 score indicates network-exploitable exposure of sensitive data that could assist in chained attacks.

MitigationApply the appropriate IBM fix for your specific Cloud Pak System version (2.3.3.7 iFix1 or later). If patching is not immediately feasible, review system configurations and access controls to limit exposure of system information to unauthenticated users.

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. Identify installed IBM Cloud Pak System version
    Run the command to retrieve the Cloud Pak System version, typically via the platform management interface or by querying the system version API endpoint
    Affected if The installed version matches 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 iFix1 (or any version between 2.3.3.0 and 2.3.3.7 iFix1 inclusive)
  2. Check for unauthenticated access to system endpoints
    Attempt to access common system information endpoints (such as system diagnostics, configuration pages, or API endpoints that return system details) without providing credentials
    Affected if Sensitive system details are returned without authentication being required or enforced
  3. Review access control configurations
    Examine the Cloud Pak System access control settings and network policies to determine which interfaces and endpoints are exposed to unauthenticated or untrusted network segments
    Affected if System information interfaces are accessible from unauthenticated network contexts
  4. Test for information disclosure via web interfaces
    Inspect web-based management interfaces, API documentation endpoints, or diagnostic pages for unexpected exposure of system configuration, version details, or internal network information
    Affected if Sensitive system details that should be restricted are visible without login or proper authorization
  5. Verify network exposure of management interfaces
    Scan network-accessible ports and services to identify management interfaces that may return system information to unauthenticated requesters
    Affected if Management or diagnostic interfaces returning sensitive data are reachable from untrusted networks without authentication

You are affected if your IBM Cloud Pak System version is 2.3.3.0 through 2.3.3.7 iFix1 and unauthenticated users can access system information through any exposed interface or endpoint.

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 the appropriate IBM fix for your specific Cloud Pak System version (2.3.3.7 iFix1 or later). If patching is not immediately feasible, review system configurations and access controls to limit exposure of system information to unauthenticated users.

Recommended fix Moderate confidence

IBM Cloud Pak System 2.3.3.8 or later (refer to IBM support for the exact fixed release)

  1. 1. Identify your current IBM Cloud Pak System version by checking the system administration console or running the appropriate version command.
  2. 2. Review the IBM Cloud Pak System support lifecycle to confirm the fixed release for this vulnerability.
  3. 3. Plan the upgrade considering your current configuration and dependencies.
  4. 4. Back up all critical data and configurations before initiating the upgrade.
  5. 5. Follow IBM's documented upgrade procedure for Cloud Pak System to the fixed release (2.3.3.8 or later, which addresses this vulnerability).
  6. 6. After upgrade, verify the fix by checking that error messages no longer expose sensitive system information.
  7. 7. Validate that all dependent applications and integrations function correctly post-upgrade.
Caveat Review IBM's upgrade documentation for potential configuration changes or migration requirements between minor releases

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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