dbcve.org
Storage ScaleApplication · Ibm

CVE-2024-31892

HIGH · 7.5 CVSS v3.1 Published 2024-12-14
Fix available
A fix is available. Upgrade to 5.1.9.7 / 5.2.2.0 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Storage Scale GUI 5.1.9.0 through 5.1.9.6 and 5.2.0.0 through 5.2.1.1 could allow a user to perform unauthorized actions after intercepting and modifying a csv file due to improper neutralization of formula elements.

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 · high confidence

IBM Storage Scale GUI versions 5.1.9.0-5.1.9.6 and 5.2.0.0-5.2.1.1 contains a CSV injection vulnerability where formula elements in CSV exports are not properly neutralized. An attacker who can intercept and modify CSV files can inject malicious spreadsheet formulas that execute unauthorized actions when users open the file.

MitigationApply IBM patches 5.1.9.7 or 5.2.1.2 and later to properly sanitize formula elements in CSV exports. Until patched, exercise extreme caution when opening CSV files from untrusted sources.

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
Storage ScaleApplication
Affected:>= 5.1.9.0, < 5.1.9.7>= 5.2.0.0, < 5.2.2.0

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Storage Scale version
    Run 'lsscsi' or check /usr/lpp/VRTSscaled/ directory for version file, or use 'mmfsadm dump version' command. Alternatively, check IBM Spectrum Scale documentation for version retrieval commands specific to your deployment.
    Affected if Version is 5.1.9.0 through 5.1.9.6, or 5.1.9.0-5.1.9.6, or 5.2.0.0-5.2.1.1 (all versions before 5.1.9.7 or 5.2.2.0)
  2. Confirm GUI component is enabled
    Check if the IBM Storage Scale GUI (formerly GPFS GUI) daemon is running. Use 'ps -ef | grep gui' or check for process 'sscg' or 'spectrum-lsf-gui'. Verify port 443 or 8443 is listening.
    Affected if GUI is installed and running, making CSV export functionality accessible
  3. Review audit or access logs for CSV export usage
    Check GUI audit logs (typically in /var/log/ibm/spectrum-scale/ or /var/log/gpfs/) for entries containing 'export' or '.csv'. Also check web server access logs for CSV download requests.
    Affected if CSV export functionality has been used; the vulnerability triggers when users export data to CSV

You are affected if your IBM Storage Scale version is 5.1.9.0-5.1.9.6 or 5.2.0.0-5.2.1.1 and the GUI CSV export feature is accessible or has been used.

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
Upgrade available Upgrade to 5.1.9.7 / 5.2.2.0 or later
Fixed in 5.1.9.75.2.2.0
Interim mitigation

Apply IBM patches 5.1.9.7 or 5.2.1.2 and later to properly sanitize formula elements in CSV exports. Until patched, exercise extreme caution when opening CSV files from untrusted sources.

Recommended fix High confidence

5.1.9.7 or later for 5.1.x branch; 5.2.2.0 or later for 5.2.x branch

  1. Identify the currently installed IBM Storage Scale version using 'lsrscale --version' or through the GUI about section
  2. For versions 5.1.9.0-5.1.9.6: Plan upgrade to version 5.1.9.7 or later
  3. For versions 5.2.0.0-5.2.1.1: Plan upgrade to version 5.2.2.0 or later
  4. Review IBM Storage Scale upgrade documentation for your specific version at www.ibm.com
  5. Schedule a maintenance window as upgrades may require downtime
  6. Back up current configuration and data
  7. Perform the upgrade following IBM's documented procedures
  8. Verify the GUI version reflects the fixed release after upgrade
Caveat Upgrades between major versions may require configuration review; ensure compatibility with your storage infrastructure

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

Fix this in Storage Scale Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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