CVE-2023-37405
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 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.36 iFix1, 2.3.3.6 iFix2, 2.3.3.7, 2.3.3.7 iFix1, 2.3.4.0, and 2.3.4.1 stores sensitive data in memory, that could be obtained by an unauthorized user.
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 · low confidenceIBM Cloud Pak System versions 2.3.3.0 through 2.3.4.1 store sensitive data in memory in a manner that allows unauthorized users to potentially obtain this data. The vulnerability appears to involve improper handling or protection of sensitive information within the system's memory space, possibly due to insufficient encryption, improper memory clearing, or inadequate access controls on memory contents.
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= 2.3.1.1= 2.3.3.0= 2.3.3.3= 2.3.3.4= 2.3.3.5= 2.3.3.6= 2.3.3.7= 2.3.4.0= 2.3.4.1= 2.3.2.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Cloud Pak System versionAccess the system administration console or use the platform management CLI tool to retrieve the installed version number. Typically found in 'About' or 'System Information' sections of the management interface, or via 'icp4acli --version' or similar platform commands.Affected if The installed version matches any of these: 2.3.1.1, 2.3.3.0, 2.3.3.3, 2.3.3.4, 2.3.3.5, 2.3.3.6, 2.3.3.7, 2.3.4.0, or 2.3.4.1
-
Identify IBM Cloud Pak System Software Suite versionCheck the installed components or platform services inventory for the Software Suite version. This may be visible in the component list within the administration dashboard or via command-line inventory queries.Affected if The Software Suite version is 2.3.2.0
-
Verify version is within the affected rangeCompare your identified version(s) against the list of affected versions. Note that the vulnerability spans multiple point releases, so any version from 2.3.1.1 through 2.3.4.1 that appears in the affected list indicates potential exposure.Affected if Any of the installed product versions exactly match the versions listed in the affected products section
You are affected if your IBM Cloud Pak System version is exactly 2.3.1.1, 2.3.3.0, 2.3.3.3, 2.3.3.4, 2.3.3.5, 2.3.3.6, 2.3.3.7, 2.3.4.0, and 2.3.4.1, or your IBM Cloud Pak System Software Suite version is exactly 2.3.2.0.
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.
From vendor dataApply IBM-provided patches or iFixes corresponding to the affected versions (2.3.3.3 through 2.3.4.1). If patches are unavailable, implement compensating controls such as restricting network access to the system, limiting privileges of users, and monitoring for unauthorized memory access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37405 — 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-2023-37405 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