dbcve.org
Powerscale OnefsApplication · Dell

CVE-2024-29170

HIGH · 8.1 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to after 9.8.0.0 or later.
See remediation →
86/100
Remediation priority · High
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 versions 8.2.x through 9.8.0.x contain a use of hard coded credentials vulnerability. An adjacent network unauthenticated attacker could potentially exploit this vulnerability, leading to information disclosure of network traffic and 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 · high confidence

Dell PowerScale OneFS versions 8.2.x through 9.8.0.x contain hardcoded credentials embedded in the firmware or configuration. An adjacent network attacker who can reach the system can use these credentials to authenticate without valid user credentials, leading to interception of network traffic and potential denial of service by abusing the gained access.

MitigationReplace hardcoded credentials with dynamically generated, unique credentials. Dell has released updates for affected versions; upgrade to a patched version or follow vendor guidance for credential rotation if patches are not immediately applicable.

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:>= 8.2.0, <= 9.8.0.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/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. Determine PowerScale OneFS version
    Run 'isi version' or check the system management interface for the installed OneFS version number
    Affected if The installed version falls within 8.2.0 through 9.8.0.0 (inclusive)
  2. Identify hardcoded credentials in configuration
    Review firmware configuration files and embedded credential storage locations for any static or default credentials that appear hardcoded rather than dynamically generated
    Affected if Any hardcoded credentials are found embedded in firmware or configuration files
  3. Check authentication configuration
    Examine the authentication and access control configuration to determine if the vulnerable credential-based authentication pathway is enabled
    Affected if The authentication method using the hardcoded credentials is active and accessible
  4. Assess network accessibility
    Verify whether the management interface or authentication service is reachable from adjacent network segments
    Affected if The system is network-accessible to adjacent attackers who could reach the authentication interface

You are affected if your PowerScale OneFS version is 8.2.0 through 9.8.0.0 and hardcoded credentials exist in your firmware or configuration that could be used for unauthenticated access.

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 a release after 9.8.0.0
Interim mitigation

Replace hardcoded credentials with dynamically generated, unique credentials. Dell has released updates for affected versions; upgrade to a patched version or follow vendor guidance for credential rotation if patches are not immediately applicable.

Recommended fix Moderate confidence

Upgrade to a version newer than 9.8.0.0 (contact Dell for the specific fixed release)

  1. Contact Dell Support or visit dell.com/support to obtain the specific security patch or updated version for PowerScale OneFS.
  2. Review the Dell PowerScale OneFS upgrade documentation and release notes for the target version.
  3. Schedule a maintenance window - upgrades may require downtime and should be performed during planned maintenance periods.
  4. Back up critical data and configuration before initiating the upgrade.
  5. Follow Dell's documented upgrade procedure for PowerScale OneFS, which typically involves using the 'isi升级' or similar upgrade utility.
  6. After upgrade, verify the system is running the patched version and confirm the hard-coded credentials vulnerability is resolved.
  7. Review audit logs for any signs of exploitation prior to patching.
Caveat Check Dell release notes for upgrade path requirements - OneFS upgrades may have specific version sequencing requirements and could have compatibility implications for existing configurations and integrated systems

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
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,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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