dbcve.org
Powerscale OnefsOperating system · Dell

CVE-2024-25959

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 9.4.0.17 / 9.5.0.8 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Dell PowerScale OneFS versions 9.4.0.x through 9.7.0.x contains an insertion of sensitive information into log file vulnerability. A low privileged local attacker could potentially exploit this vulnerability, leading to sensitive information disclosure, escalation of privileges.

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

Dell PowerScale OneFS versions 9.4.0.x through 9.7.0.x contains a vulnerability where sensitive information is written to log files. A low-privileged local attacker with filesystem access can potentially read these logs to obtain sensitive data and escalate privileges to higher permission levels.

MitigationUpgrade to a version beyond 9.7.0.x or apply Dell-supplied security patches. Until patched, limit local access to the system and restrict filesystem permissions on log directories.

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
Powerscale OnefsOperating system
Affected:>= 9.4.0, < 9.4.0.17>= 9.5.0.0, < 9.5.0.8>= 9.6.1, < 9.7.0.2

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

CVSS:3.1/AV:L/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 checks

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

  1. Determine the installed OneFS version
    Run the command 'isi version' or 'isi status' on the PowerScale system CLI to retrieve the installed firmware version
    Affected if The version falls within 9.4.0.0 through 9.4.0.16, 9.5.0.0 through 9.5.0.7, or 9.6.1 through 9.7.0.1
  2. Review log file permissions
    Use 'ls -la' on log directories such as /var/log/, /ifs/*/logs/, or the platform log location to check who can read log files
    Affected if Log files or directories are readable by non-administrative users or have overly permissive access controls
  3. Inspect log contents for sensitive data
    Search log files using 'grep' or a text viewer for patterns that may indicate exposed credentials, passwords, tokens, or API keys written in plain text
    Affected if Log files contain sensitive information such as plaintext passwords, authentication tokens, or credential data that should not be logged
  4. Check for low-privileged local accounts
    Review local user accounts on the system using 'isi auth' commands or user management tools to identify accounts with limited permissions
    Affected if Low-privileged local accounts exist and have filesystem access to log directories where sensitive data may be written

A system is affected if it runs OneFS version 9.4.0.0-9.4.0.16, 9.5.0.0-9.5.0.7, or 9.6.1-9.7.0.1 and log files containing sensitive data are accessible to low-privileged local users with filesystem access.

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 9.4.0.17 / 9.5.0.8 / 9.7.0.2 or later
Fixed in 9.4.0.179.5.0.89.7.0.2
Interim mitigation

Upgrade to a version beyond 9.7.0.x or apply Dell-supplied security patches. Until patched, limit local access to the system and restrict filesystem permissions on log directories.

Recommended fix Moderate confidence

9.7.0.2 (or branch-specific: 9.4.0.17+, 9.5.0.8+)

  1. 1. Identify current OneFS version using 'isi version' command or via the web administration UI
  2. 2. Create a complete backup of the OneFS configuration and ensure data is protected
  3. 3. Review Dell PowerScale OneFS upgrade compatibility matrix and release notes for the target version
  4. 4. Download the appropriate fixed version from Dell Support: 9.4.0.17 or later for 9.4.x branch, 9.5.0.8 or later for 9.5.x branch, or 9.7.0.2 or later for 9.6.x/9.7.x branch
  5. 5. Plan maintenance window as OneFS upgrades may require cluster downtime
  6. 6. Follow Dell official OneFS upgrade procedure documentation to apply the patch
Caveat OneFS upgrades require careful planning - review upgrade compatibility matrix and test in non-production environment first; cluster may require brief downtime

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

Fix this in Powerscale Onefs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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