Powerscale OnefsOperating system · Dell

CVE-2024-22463

CRITICAL · 9.1 CVSS v3.1 Developing Published 2024-03-04
Fix available
A fix is available. Upgrade to 9.4.0.17 / 9.5.0.6 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 8.2.x through 9.6.0.x contains a use of a broken or risky cryptographic algorithm vulnerability. A remote unprivileged attacker could potentially exploit this vulnerability, leading to compromise of confidentiality and integrity of sensitive information

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-31.

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.0, < 9.4.0.17>= 9.5.0.0, < 9.5.0.6= 9.6.1

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
Upgrade available Upgrade to 9.4.0.17 / 9.5.0.6 or later
Fixed in 9.4.0.179.5.0.6
Recommended fix High confidence

9.4.0.17 or later (9.4.x series); 9.5.0.6 or later (9.5.x series); 9.6.2 or later (9.6.x series)

  1. 1. Identify the current PowerScale OneFS version running on the system using 'isi version' or through the web UI.
  2. 2. Determine the appropriate upgrade path based on current version: if on 8.2.x - 9.3.x, upgrade to 9.4.0.17 or later; if on 9.4.x, upgrade to 9.4.0.17 or later; if on 9.5.x, upgrade to 9.5.0.6 or later; if on 9.6.1, upgrade to 9.6.2 or later.
  3. 3. Review Dell PowerScale OneFS upgrade documentation and release notes for the target version.
  4. 4. Create a backup or snapshot of the system before proceeding with the upgrade.
  5. 5. Schedule a maintenance window as upgrades require downtime.
  6. 6. Download the validated upgrade package from Dell Support (www.dell.com/support).
  7. 7. Execute the upgrade following Dell's documented procedure, typically via 'isi upgrade' command or through the web UI.
  8. 8. Verify the upgrade completed successfully and confirm the new version is running with 'isi version'.
Caveat Upgrading OneFS major versions may require cluster downtime and may have compatibility implications with connected clients/integrations; review release notes for any known issues

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 $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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