dbcve.org
Powerscale OnefsApplication · Dell

CVE-2024-39578

MEDIUM · 6.3 CVSS v3.1 Published 2024-08-31
Fix available
A fix is available. Upgrade to 9.7.1.2 or later.
See remediation →
65/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.1 contains a UNIX symbolic link (symlink) following vulnerability. A local high privileged attacker could potentially exploit this vulnerability, leading to denial of service, information tampering.

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.1 contains a symlink following vulnerability where the software improperly handles symbolic links, allowing a local high-privileged attacker to cause denial of service or tamper with information through malicious symlink manipulation.

MitigationApply the vendor-provided patch from Dell for PowerScale OneFS. Until patched, limit local high-privileged access and monitor for suspicious symlink creation in sensitive directories.

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.0, < 9.7.1.2

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
Low
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/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 PowerScale OneFS version
    Run 'isi version' or check the OneFS web interface under Cluster Management > General for the installed OneFS version number.
    Affected if The installed version is 8.2.2.x through 9.8.0.1, or specifically 9.8.0.0, or falls between 8.2.2.0 and 9.7.1.2 (exclusive of 9.7.1.2).
  2. Audit symlinks in system directories
    Use 'find / -type l -ls' or check specific sensitive directories like /ifs, /var, /home for symbolic links. Compare against known-good baseline if available.
    Affected if Unexpected or newly created symbolic links exist in system directories, particularly pointing outside expected paths.
  3. Review audit logs for symlink operations
    Check OneFS audit logs (isi audit' command) and system logs for entries involving symlink creation, modification, or access, especially from high-privileged accounts.
    Affected if Logs show unusual symlink creation or manipulation by privileged users that was not authorized or expected.
  4. Identify high-privileged local access
    Review which users or accounts have elevated (root, admin, or ISI_ADMIN) privileges on the OneFS cluster using 'isi auth' commands or the Access zone settings.
    Affected if Multiple high-privileged accounts exist beyond the known administrator baseline, or unauthorized privileged access is detected.

A system is affected if it runs a vulnerable PowerScale OneFS version (8.2.2.0 through 9.7.1.2 or exactly 9.8.0.0 through 9.8.0.1) and has sensitive directory symlinks that could be exploited by a local high-privileged attacker.

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.7.1.2 or later
Fixed in 9.7.1.2
Interim mitigation

Apply the vendor-provided patch from Dell for PowerScale OneFS. Until patched, limit local high-privileged access and monitor for suspicious symlink creation in sensitive directories.

Recommended fix Moderate confidence

OneFS 9.7.1.2 or later, or OneFS 9.8.0.2 or later

  1. 1. Identify the current PowerScale OneFS version by running 'isi version' or checking the OneFS web UI.
  2. 2. Plan an upgrade to OneFS version 9.7.1.2 or later, or version 9.8.0.2 or later if using the 9.8.x branch.
  3. 3. Review Dell PowerScale OneFS upgrade documentation and release notes for the target version.
  4. 4. Create a backup of critical data and configuration before upgrading.
  5. 5. Schedule a maintenance window as upgrades require cluster downtime.
  6. 6. Follow Dell's recommended upgrade procedure, typically using 'isi upgrade' command or the OneFS web UI.
  7. 7. After upgrade, verify the version running 'isi version' and confirm the security patch is applied.
  8. 8. Test critical workflows to ensure the upgrade did not introduce issues.
Caveat Review OneFS release notes for any configuration or feature changes between versions; upgrades may require cluster downtime and have specific compatibility requirements

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

Fix this in Powerscale Onefs Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
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,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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