dbcve.org
Powerscale OnefsApplication · Dell

CVE-2024-37134

MEDIUM · 6.7 CVSS v3.1 Published 2024-07-02
Fix available
A fix is available. Upgrade to 9.5.1.0 / 9.7.1.0 or later.
See remediation →
69/100
Remediation priority · Elevated
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.0 contain an improper privilege management vulnerability. A local high privileged attacker could potentially exploit this vulnerability to gain root-level access.

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 8.2.2.x through 9.8.0.0 contains an improper privilege management vulnerability allowing a local high-privileged attacker to escalate to root-level access. This is a local privilege escalation flaw rather than a remote code execution issue.

MitigationApply the vendor-provided patch or upgrade to a fixed OneFS version as specified in Dell's security advisory. Since this requires local high-privileged access, ensure strict access controls and monitor for unauthorized privilege escalation attempts until the patch is applied.

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.5.1.0>= 9.6.0, < 9.7.1.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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. Identify the installed PowerScale OneFS version
    Run the command 'isi version' or 'isi -v' on the OneFS CLI to display the current firmware version
    Affected if The displayed version falls within any of these ranges: 9.8.0.0 exactly; 8.2.2 through 9.5.0.x; 9.6.0 through 9.7.0.x
  2. Verify the full version string
    Run 'isi_gconfig --version' or check the OneFS web interface under Access > Cluster > Identity for the complete version number including build
    Affected if The version matches 9.8.0.0, or is >= 8.2.2 but < 9.5.1.0, or is >= 9.6.0 but < 9.7.1.0
  3. Confirm the vulnerability scope
    This is a local privilege escalation requiring an attacker to already have high-privileged (non-root) access to the system
    Affected if The attacker already has elevated local access and the OneFS version is within the affected ranges listed above

You are affected if your PowerScale OneFS version is 9.8.0.0, between 8.2.2 and 9.5.0.x inclusive, or between 9.6.0 and 9.7.0.x inclusive.

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.5.1.0 / 9.7.1.0 or later
Fixed in 9.5.1.09.7.1.0
Interim mitigation

Apply the vendor-provided patch or upgrade to a fixed OneFS version as specified in Dell's security advisory. Since this requires local high-privileged access, ensure strict access controls and monitor for unauthorized privilege escalation attempts until the patch is applied.

Recommended fix Moderate confidence

OneFS 9.5.1.0 or later (for 8.2.2-9.4.x branches), 9.7.1.0 or later (for 9.6.x branch), or 9.8.0.1 or later (for 9.8.0 branch)

  1. Verify current OneFS version using 'isi version' command
  2. Schedule a maintenance window for the upgrade
  3. Back up critical data and configuration using 'isi backup' or cluster snapshot
  4. Download the appropriate OneFS upgrade ISO from Dell Support (versions 9.5.1.0+, 9.7.1.0+, or 9.8.0.1+ depending on your current branch)
  5. Upload the upgrade image to the cluster using 'isi cluster images upload'
  6. Initiate upgrade with 'isi cluster images install <image>' and confirm the one-node-at-a-time upgrade process
  7. Verify post-upgrade functionality and ensure no services are degraded
  8. Confirm the vulnerability is remediated by verifying the version is beyond the affected ranges
Caveat OneFS upgrades require careful planning; rolling upgrades are one-node-at-a-time and may impact performance during maintenance window; always review Dell upgrade documentation and run pre-upgrade checks

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

Fix this in Powerscale Onefs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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