CVE-2024-47239
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 · uneditedDell PowerScale OneFS versions 8.2.2.x through 9.9.0.0 contain an uncontrolled resource consumption 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 confidenceDell PowerScale OneFS versions 8.2.2.x through 9.9.0.0 contain an uncontrolled resource consumption vulnerability. A remote low-privileged attacker could exploit this by exhausting system resources, leading to denial of service.
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>= 9.5.0.0, < 9.5.1.2>= 9.8.0.0, < 9.9.0.1>= 8.2.2.0, < 9.7.1.3>= 9.4.0, < 9.4.0.20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify PowerScale OneFS versionRun the command 'isi version' or 'isi status' on the PowerScale CLI to retrieve the installed OneFS version numberAffected if The version displayed matches any of the affected ranges: 9.5.0.0 through 9.5.1.1, 9.8.0.0 through 9.9.0.0, 8.2.2.0 through 9.7.1.2, or 9.4.0 through 9.4.0.19
-
Verify the full version stringRun 'isi get version' or check the System Management UI under About > Version to confirm the complete version including build numberAffected if The version falls within the vulnerable ranges as specified above
-
Check system resource statusUse 'isi status -d' or the OneFS web UI dashboard to observe CPU, memory, and network utilization patterns for abnormal consumptionAffected if Unusually high resource consumption is observed without an explanatory workload cause, potentially indicating exploitation
-
Review authentication logs for low-privilege activityExamine OneFS audit logs under /var/log/audit/ or via the Security > Audit Logs UI for repeated authentication attempts from low-privilege accountsAffected if There is evidence of many failed or successful requests from low-privileged users that correlate with resource exhaustion symptoms
A system is affected if it runs any Dell PowerScale OneFS version within the ranges 9.5.0.0-9.5.1.1, 9.8.0.0-9.9.0.0, 8.2.2.0-9.7.1.2, or 9.4.0-9.4.0.19 and exhibits unexplained resource exhaustion.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.4.0.209.5.1.29.7.1.3
Apply the vendor-supplied security patch for Dell PowerScale OneFS. Contact Dell Support for the specific patched version and update all affected systems.
9.4.0.20, 9.5.1.2, 9.7.1.3, or 9.9.0.1 depending on current branch
- 1. Identify the current OneFS version by running 'isi version' or checking the cluster management UI
- 2. Based on current version, determine the minimum fixed release needed: for 9.4.x upgrade to 9.4.0.20+, for 8.2.2.x-9.5.x upgrade to 9.5.1.2+, for 9.6.x-9.7.x upgrade to 9.7.1.3+, for 9.8.x-9.9.0.0 upgrade to 9.9.0.1+
- 3. Download the corresponding OneFS patch from Dell Support (www.dell.com/powerscale) under Drivers & Downloads
- 4. Create a backup or snapshot of the cluster before applying the update
- 5. Apply the update via the OneFS web UI under Cluster Management > Updates, or via CLI using 'isi upgrade' command
- 6. Verify the upgrade completed successfully and the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-47239 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47239 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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