dbcve.org
Elastic Storage SystemApplication · Ibm

CVE-2022-43869

MEDIUM · 6.5 CVSS v3.1 Published 2023-02-12
Fix available
A fix is available. Upgrade to after 6.1.4.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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 Spectrum Scale (5.1.0.0 through 5.1.2.8 and 5.1.3.0 through 5.1.5.1) and IBM Elastic Storage System (6.1.0.0 through 6.1.2.4 and 6.1.3.0 through 6.1.4.1) could allow an authenticated user to cause a denial of service through the GUI using a format string attack. IBM X-Force ID: 239539.

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

A detailed technical summary for this CVE is being prepared.

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
Elastic Storage SystemApplication
Affected:>= 6.1.0.0, <= 6.1.2.4>= 6.1.3.0, <= 6.1.4.1
Spectrum ScaleApplication
Affected:>= 5.1.0.0, <= 5.1.2.8>= 5.1.3.0, <= 5.1.5.1

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 a release after 6.1.4.1
Vendor patch www.ibm.com →
Recommended fix Moderate confidence

IBM Spectrum Scale 5.1.5.2+ or 5.1.x latest stable; IBM Elastic Storage System 6.1.4.2+ or 6.1.x latest stable

  1. 1. Identify the current version of IBM Spectrum Scale or IBM Elastic Storage System by running: mmgetversion (for Spectrum Scale) or the appropriate system query command
  2. 2. Plan an upgrade to a fixed version that is beyond the vulnerable version ranges
  3. 3. For IBM Spectrum Scale: upgrade to version 5.1.5.2 or later (or the latest 5.1.x stable release)
  4. 4. For IBM Elastic Storage System: upgrade to version 6.1.4.2 or later (or the latest 6.1.x stable release)
  5. 5. Before upgrading in production, test the new version in a staging environment to ensure compatibility with your existing workloads
  6. 6. During the maintenance window, perform the upgrade following IBM's standard upgrade procedures for your product
  7. 7. After upgrade, verify the GUI is accessible and the vulnerability is remediated by confirming the version and testing GUI functionality
  8. 8. Review the IBM support page https://www.ibm.com/support/pages/node/6909465 for any product-specific upgrade instructions or additional patch requirements
Caveat Review release notes for any configuration or feature changes between your current version and the target version before upgrading

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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