Powerscale OnefsOperating system · Dell

CVE-2024-25961

MEDIUM · 6.7 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 9.5.0.8 / 9.7.0.2 or later.
See remediation →
69/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 8.2.2.x through 9.7.0.x contains an improper privilege management vulnerability. A local high privileged attacker could potentially exploit this vulnerability, leading to 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 · high confidence

Dell PowerScale OneFS versions 8.2.2.x through 9.7.0.x contains an improper privilege management vulnerability. A local attacker who already has high-level privileges can exploit this flaw to escalate their privileges further, potentially gaining administrative or root-level access to the storage system.

MitigationApply the vendor patch or upgrade to a fixed OneFS version beyond 9.7.0.x. Until then, strictly limit local administrative access to trusted personnel and monitor for unauthorized privilege escalation attempts.

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:>= 8.2.2.0, <= 9.3.0>= 9.4.0, <= 9.4.0.16>= 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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 OneFS version
    Run 'isi version' or 'isi get version' command on the PowerScale node, or check the OneFS web UI under Access > About > Version
    Affected if Version falls within ranges: 8.2.2.0-9.3.0, 9.4.0-9.4.0.16, 9.5.0.0-9.5.0.7, or 9.6.1-9.7.0.1
  2. Confirm version is within affected range
    Compare the installed version number against the affected ranges. Note that versions 9.3.1-9.3.x, 9.4.1-9.4.x (beyond .16), 9.5.0.8+, and 9.7.0.2+ are NOT affected
    Affected if Installed version matches any of the four affected ranges listed in the CVE
  3. Verify current privilege state
    Check for unexpected accounts with administrator or root-level privileges using 'isi auth' commands or review /var/log/audit logs for privilege changes
    Affected if New administrative accounts exist or privilege modifications occurred without documented approval

The environment is affected if the installed OneFS version falls within any of the four vulnerable version ranges AND the system has untrusted local users with high-level privileges who could attempt escalation.

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.5.0.8 / 9.7.0.2 or later
Fixed in 9.5.0.89.7.0.2
Interim mitigation

Apply the vendor patch or upgrade to a fixed OneFS version beyond 9.7.0.x. Until then, strictly limit local administrative access to trusted personnel and monitor for unauthorized privilege escalation attempts.

Recommended fix Moderate confidence

9.7.0.2 or later (addresses all affected version ranges)

  1. 1. Back up all critical data and configurations on the PowerScale OneFS system
  2. 2. Review Dell PowerScale OneFS upgrade documentation and release notes for version 9.7.0.2 or later
  3. 3. Plan maintenance window as upgrade will require system downtime
  4. 4. Download the fixed OneFS version (9.7.0.2 or later) from Dell support portal
  5. 5. Execute upgrade following Dell's documented upgrade procedure
  6. 6. Verify the upgrade completed successfully and system is operational
  7. 7. Confirm the privilege management vulnerability is resolved
Caveat OneFS upgrades may require downtime and could have compatibility implications; review release notes for breaking changes before upgrading

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

Fix this in Powerscale Onefs Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
40.0 hours of engineering $6,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25961 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