dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2023-25941

HIGH · 7.8 CVSS v3.1 Published 2023-04-04
Fix available
A fix is available. Upgrade to 9.2.1.22 / 9.4.0.13 or later.
See remediation →
80/100
Remediation priority · High
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
Dell PowerScale OneFS versions 8.2.x-9.5.0.x contain an elevation of privilege vulnerability. A low-privileged local attacker could potentially exploit this vulnerability, leading to Denial of service, escalation of privileges, and information disclosure. This vulnerability breaks the compliance mode guarantee.

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
How this class of weakness works · CWE-276

Files, directories, or resources ship with permissions more open than they need to be, so unintended users can read or modify them. Attackers look for exactly these loose defaults. Remediation means tightening permissions to the minimum required and verifying them at install and at runtime.

General guidance for the incorrect default permissions class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Emc Powerscale OnefsOperating system
Affected:>= 9.1.0.0, <= 9.1.0.28>= 9.2.1.0, < 9.2.1.22>= 9.4.0.0, < 9.4.0.13

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 9.2.1.22 / 9.4.0.13 or later
Fixed in 9.2.1.229.4.0.13
Vendor patch www.dell.com →
Recommended fix High confidence

Upgrade to OneFS 9.1.0.29 or later for 9.1.x branches; 9.2.1.22 or later for 9.2.x branches; 9.4.0.13 or later for 9.4.x branches

  1. 1. Identify the current PowerScale OneFS version running on the system using 'isi version' or the OneFS web UI
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release: For 9.1.0.x branches, upgrade to 9.1.0.29 or later; For 9.2.1.x branches, upgrade to 9.2.1.22 or later; For 9.4.0.x branches, upgrade to 9.4.0.13 or later
  3. 3. Review Dell PowerScale OneFS upgrade documentation and release notes for the target version
  4. 4. Schedule a maintenance window as upgrades require cluster downtime
  5. 5. Back up the OneFS cluster configuration and verify data integrity before proceeding
  6. 6. Perform the upgrade following Dell's documented upgrade procedure, typically using 'isi upgrade' command or OneFS web UI
  7. 7. After upgrade completion, verify the new version is running using 'isi version'
  8. 8. Confirm the vulnerability is resolved by checking the security patch level matches or exceeds the fixed versions
Caveat PowerScale OneFS upgrades require scheduled downtime and should be tested in a non-production environment first; review release notes for any behavior changes or deprecated features in the target version

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,250. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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