dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2022-45101

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 9.1.0.25 / 9.2.1.18 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 9.0.0.x - 9.4.0.x, contains an Improper Handling of Insufficient Privileges vulnerability in NFS. A remote unauthenticated attacker could potentially exploit this vulnerability, leading to information disclosure and remote execution.

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.0.0.x through 9.4.0.x contain an improper handling of insufficient privileges vulnerability in the NFS service. A remote unauthenticated attacker can exploit this NFS vulnerability to gain unauthorized access, disclose sensitive information, and achieve remote code execution on the affected system.

MitigationUpgrade Dell PowerScale OneFS to version 9.5.0.0 or later to address this vulnerability. If immediate patching is not possible, restrict NFS access to trusted networks and implement network segmentation to limit exposure to unauthenticated attackers.

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
Emc Powerscale OnefsOperating system
Affected:>= 9.1.0.0, < 9.1.0.25>= 9.2.1.0, < 9.2.1.18>= 9.4.0.0, < 9.4.0.9

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify NFS service is enabled on the system
    Run 'isi nfs status' or check the OneFS web UI under Protocols > NFS to see if NFS is enabled and running
    Affected if NFS is enabled and running - the vulnerability only affects systems with the NFS service active
  2. Determine the installed OneFS version
    Run 'isi version' or 'isi getver' from the OneFS command line to retrieve the exact version number
    Affected if The installed version is one of: 9.1.0.0 through 9.1.0.24, 9.2.1.0 through 9.2.1.17, or 9.4.0.0 through 9.4.0.8
  3. Check for exposed NFS ports from untrusted networks
    Review firewall rules and network access controls to determine if NFS ports (111, 2049, etc.) are accessible from untrusted or external networks
    Affected if NFS is exposed to untrusted networks or the internet without network segmentation or access controls

The system is affected if NFS is enabled and the installed OneFS version falls within 9.1.0.0-9.1.0.24, 9.2.1.0-9.2.1.17, or 9.4.0.0-9.4.0.8, and NFS is accessible to untrusted network segments.

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.1.0.25 / 9.2.1.18 / 9.4.0.9 or later
Fixed in 9.1.0.259.2.1.189.4.0.9
Interim mitigation

Upgrade Dell PowerScale OneFS to version 9.5.0.0 or later to address this vulnerability. If immediate patching is not possible, restrict NFS access to trusted networks and implement network segmentation to limit exposure to unauthenticated attackers.

Recommended fix High confidence

Upgrade to the latest available version in your current branch: 9.1.0.25+ (9.1.0.x), 9.2.1.18+ (9.2.1.x), or 9.4.0.9+ (9.4.0.x)

  1. Identify currently installed PowerScale OneFS version using 'isi version' or OneFS web UI
  2. Determine which version branch you are on (9.1.0.x, 9.2.1.x, or 9.4.0.x)
  3. For 9.1.0.x branch: Upgrade to version 9.1.0.25 or later
  4. For 9.2.1.x branch: Upgrade to version 9.2.1.18 or later
  5. For 9.4.0.x branch: Upgrade to version 9.4.0.9 or later
  6. Download the upgrade ISO from Dell Support (www.dell.com/support)
  7. Follow Dell PowerScale OneFS upgrade procedure: Boot from ISO, run 'isi upgrade' command, or use OneFS web UI
  8. Verify successful upgrade with 'isi version' command
Caveat Standard OneFS upgrade considerations apply: cluster should have adequate free space, upgrade should be performed during maintenance window, and rollback may require cluster backup. NFS services may briefly interrupt during upgrade.

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

Fix this in Emc Powerscale Onefs Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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