dbcve.org
Powerscale OnefsOperating system · Dell

CVE-2022-29098

HIGH · 7.5 CVSS v3.1 Published 2022-06-01
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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.0.x through 9.3.0.x, contain a weak password requirement vulnerability. An administrator may create an account with no password. A remote attacker may potentially exploit this leading to a user account compromise.

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
Powerscale OnefsOperating system
Affected:= 9.0.0= 9.1.0= 9.1.1= 9.2.0= 9.2.1= 9.3.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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
Patch available Apply the vendor patch
Vendor patch www.dell.com →
Recommended fix Moderate confidence

OneFS 9.3.0 or later stable release (verify specific fixed version in Dell DSA-2022-082)

  1. 1. Identify the current PowerScale OneFS version running on the cluster using 'isi version' or through the web UI.
  2. 2. Review the Dell Support Article DSA-2022-082 for the specific security update and recommended fixed version.
  3. 3. Schedule a maintenance window for the upgrade, ensuring proper backup of cluster configuration.
  4. 4. Download the patched OneFS iso/image from Dell Support portal for the fixed release (version 9.3.0 or later).
  5. 5. Follow standard OneFS upgrade procedure: upload the upgrade package, verify integrity, and initiate the upgrade.
  6. 6. After upgrade, verify the new version is installed using 'isi version'.
  7. 7. Create a new test account and verify that password complexity requirements are enforced (accounts cannot be created without a password).
  8. 8. Review existing user accounts and ensure all have strong passwords meeting the new requirements.
Caveat Standard OneFS upgrade risks apply - ensure cluster backup and review Dell upgrade guide for pre-requisites

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

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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