Emc Powerscale OnefsOperating system · Dell

CVE-2022-34378

MEDIUM · 5.5 CVSS v3.1 Published 2022-09-02
Fix available
A fix is available. Upgrade to after 9.4.0.3 or later.
See remediation →
57/100
Remediation priority · Elevated
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 9.0.0 up to and including 9.1.0.20, 9.2.1.13, 9.3.0.6, and 9.4.0.3, contain a relative path traversal vulnerability. A low privileged local attacker could potentially exploit this vulnerability, leading to denial of service.

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

A detailed technical summary for this CVE is being prepared.

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.20>= 9.2.1.0, <= 9.2.1.13>= 9.3.0.0, <= 9.3.0.6>= 9.4.0.0, <= 9.4.0.3

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 a release after 9.4.0.3
Vendor patch www.dell.com →
Recommended fix Moderate confidence

9.1.0.21, 9.2.1.14, 9.3.0.7, or 9.4.0.4 (first patched version in respective release branch)

  1. 1. Identify the current installed version of Dell PowerScale OneFS using 'isi version' or through the OneFS web UI under Cluster Management > Overview
  2. 2. Based on the current version, upgrade to the first patched version in that release line: For 9.1.x - upgrade to 9.1.0.21 or later; For 9.2.x - upgrade to 9.2.1.14 or later; For 9.3.x - upgrade to 9.3.0.7 or later; For 9.4.x - upgrade to 9.4.0.4 or later
  3. 3. Download the updated OneFS ISO from the Dell Support website (support.dell.com) using your service tag
  4. 4. Create a OneFS upgrade job via the web UI (Cluster Management > Updates > Upgrade) or CLI using 'isi upgrade' commands
  5. 5. Before upgrading, run pre-upgrade checks using 'isi upgrade precheck' to verify cluster health and compatibility
  6. 6. Execute the upgrade and monitor progress through the OneFS UI or 'isi upgrade status'
  7. 7. After upgrade completes, verify the new version is installed and the vulnerability is resolved
Caveat Standard OneFS upgrade considerations apply - review release notes for any features deprecated or changed between versions; ensure adequate cluster capacity for upgrade process

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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