dbcve.org
Powerscale OnefsApplication · Dell

CVE-2024-49602

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 9.4.0.20 / 9.5.1.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Versions 8.2.2.x through 9.8.0.x contain an improper resource unlocking vulnerability. A remote low privileged 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 · moderate confidence

Dell PowerScale OneFS contains an improper resource unlocking vulnerability where a low-privileged remote attacker can cause resource locks to not be properly released, leading to resource exhaustion and denial of service. The vulnerability exists across versions 8.2.2.x through 9.8.0.x.

MitigationApply the vendor-supplied patch or upgrade to a patched OneFS version beyond 9.8.0.x. Coordinate during a maintenance window as the fix requires a software update.

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
Powerscale OnefsApplication
Affected:= 9.8.0.0>= 8.2.2, < 9.7.1.3>= 9.4.0, < 9.4.0.20>= 9.5.0.0, < 9.5.1.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Check OneFS version via CLI
    Run the command `isi version` or `isi status` on the PowerScale node to retrieve the installed OneFS version number
    Affected if The displayed version matches any of these ranges: 9.8.0.0 exactly; 8.2.2 through 9.7.1.2; 9.4.0 through 9.4.0.19; 9.5.0.0 through 9.5.1.0
  2. Check OneFS version via web UI
    Log into the PowerScale web administration interface and navigate to the dashboard or system information page to view the OneFS version
    Affected if The version shown falls within the affected ranges listed above
  3. Verify all nodes in cluster
    If running a cluster, run `isi_cluster_nodes` or check each node individually to confirm the version is consistent across all nodes
    Affected if Any node in the cluster runs an affected version
  4. Document current version for remediation tracking
    Record the exact OneFS version string from the version check for comparison against patched releases
    Affected if The version is confirmed to be in the affected range and requires patching

A system is affected if it runs Dell PowerScale OneFS version 9.8.0.0, or any version from 8.2.2 up to 9.7.1.2, 9.4.0 to 9.4.0.19, or 9.5.0.0 to 9.5.1.0.

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.4.0.20 / 9.5.1.1 / 9.7.1.3 or later
Fixed in 9.4.0.209.5.1.19.7.1.3
Interim mitigation

Apply the vendor-supplied patch or upgrade to a patched OneFS version beyond 9.8.0.x. Coordinate during a maintenance window as the fix requires a software update.

Recommended fix Moderate confidence

Upgrade to the latest available OneFS version in your release line: 9.4.0.20+, 9.5.1.1+, 9.7.1.3+, or 9.8.0.x (latest)

  1. 1. Identify the current OneFS version by running 'isi version' or checking the cluster management UI
  2. 2. For OneFS 9.8.0.0: upgrade to the latest 9.8.0.x release that contains the security fix
  3. 3. For OneFS 9.4.0.x: upgrade to 9.4.0.20 or later
  4. 4. For OneFS 9.5.0.x: upgrade to 9.5.1.1 or later
  5. 5. For OneFS 9.7.x (>= 8.2.2): upgrade to 9.7.1.3 or later
  6. 6. Before upgrading, review the OneFS upgrade pre-check requirements and ensure adequate cluster capacity
  7. 7. Perform the upgrade during a maintenance window as the cluster will require a brief restart
  8. 8. After upgrade, verify the version and confirm the vulnerability is resolved
Caveat OneFS upgrades require a brief cluster outage and should be performed during scheduled maintenance windows; always review release notes for known issues before upgrading

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

Fix this in 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-2024-49602 — 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-2024-49602 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