dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2022-45099

HIGH · 7.8 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 9.1.0.24 / 9.2.1.18 or later.
See remediation →
80/100
Remediation priority · High
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-9.4.x, contain a weak encoding for a NDMP password. A malicious and privileged local attacker could potentially exploit this vulnerability, leading to a full system compromise

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.x through 9.4.x use weak encoding (rather than proper encryption or hashing) for NDMP backup protocol passwords. A local attacker with privileged access can decode the weakly encoded password to gain full system compromise.

MitigationApply vendor-supplied patch when available; until then, strictly limit local privileged access and monitor for suspicious access to NDMP configuration.

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
Emc Powerscale OnefsOperating system
Affected:>= 9.1.0.0, < 9.1.0.24>= 9.2.1.0, < 9.2.1.18>= 9.3.0.0, < 9.3.0.7>= 9.4.0.0, < 9.4.0.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Check PowerScale OneFS version
    Run 'isi version' or access the OneFS web interface under Cluster Management > Hardware to identify the installed OneFS version
    Affected if The installed version falls within any of these ranges: 9.1.0.0 through 9.1.0.23, 9.2.1.0 through 9.2.1.17, 9.3.0.0 through 9.3.0.6, or 9.4.0.0 through 9.4.0.8
  2. Verify NDMP backup service status
    Run 'isi ndmp status' or check NDMP configuration via OneFS web interface under Protocols > NDMP to determine if NDMP is enabled
    Affected if NDMP daemon or service is running and accepting connections
  3. Identify NDMP user configuration
    Run 'isi ndmp users list' or examine /usr/local/etc/ndmpd/ndmpd.conf (if accessible) to list configured NDMP users
    Affected if NDMP users exist with stored credentials in configuration
  4. Inspect NDMP password storage
    Examine NDMP configuration files for base64 or otherwise encoded password strings rather than properly hashed values
    Affected if Stored NDMP credentials use simple encoding (base64 or similar) instead of salted password hashes

Your environment is affected if the OneFS version is within the affected ranges AND NDMP is enabled with stored credentials using weak encoding.

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.1.0.24 / 9.2.1.18 / 9.3.0.7 or later
Fixed in 9.1.0.249.2.1.189.3.0.7
Interim mitigation

Apply vendor-supplied patch when available; until then, strictly limit local privileged access and monitor for suspicious access to NDMP configuration.

Recommended fix High confidence

9.1.0.24 (for 9.1.x), 9.2.1.18 (for 9.2.x), 9.3.0.7 (for 9.3.x), or 9.4.0.9 (for 9.4.x)

  1. Review Dell PowerScale OneFS release notes for your current version branch to understand changes in the target version
  2. Create a complete backup of critical data and cluster configuration
  3. Schedule the upgrade during a maintenance window with minimal production impact
  4. Upgrade to the minimum fixed version for your current branch: 9.1.0.24 (if on 9.1.x), 9.2.1.18 (if on 9.2.x), 9.3.0.7 (if on 9.3.x), or 9.4.0.9 (if on 9.4.x)
  5. Alternatively, upgrade to the latest available patch within your major version line to benefit from additional fixes
  6. After upgrade, verify NDMP configuration and confirm the password encoding mechanism has been updated
  7. Validate system functionality and cluster health post-upgrade
Caveat Standard PowerScale OneFS upgrade considerations apply - review Dell compatibility matrices and test in non-production environment first

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

Fix this in Emc 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-2022-45099 — 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-2022-45099 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