dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2023-22572

HIGH · 7.8 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 9.1.0.27 / 9.2.1.20 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 9.1.0.x-9.4.0.x contain an insertion of sensitive information into log file vulnerability in change password api. A low privilege local attacker could potentially exploit this vulnerability, leading to system takeover.

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 contains a vulnerability in the change password API where sensitive information (likely plaintext passwords) is written to log files. A low-privilege local attacker with file system access can read these logs to obtain credentials and escalate to full system compromise.

MitigationApply vendor patches for CVE-2023-22572 when available. In the interim, restrict access to log files and consider rotating credentials that may have been exposed through logging.

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.27>= 9.2.1.0, < 9.2.1.20>= 9.4.0.0, < 9.4.0.11

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. Determine the installed OneFS version
    Run 'isi version' or check the OneFS web UI dashboard for the current firmware version
    Affected if The version falls within 9.1.0.0-9.1.0.26, 9.2.1.0-9.2.1.19, or 9.4.0.0-9.4.0.10 (these are the unpatched versions)
  2. Identify log files containing password change operations
    Search system log directories (typically under /var/log or /ifs/.ifsvar/logs) for entries related to password change API calls
    Affected if Log entries exist that contain plaintext passwords or sensitive credential data in change password operation records
  3. Review access to log file directories
    Inspect file permissions on log directories to determine if low-privilege local users can read log files
    Affected if Log files are readable by non-privileged users or the 'everyone' group, allowing local attacker access to credentials
  4. Check for recent password change API activity
    Review authentication and system event logs for password change API invocations, looking for any password data appearing in the log content
    Affected if Plaintext passwords are visible in any password change or account modification log entries

The environment is affected if OneFS version is in the unpatched ranges AND log files contain plaintext passwords from change password API operations accessible to low-privilege users.

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.27 / 9.2.1.20 / 9.4.0.11 or later
Fixed in 9.1.0.279.2.1.209.4.0.11
Interim mitigation

Apply vendor patches for CVE-2023-22572 when available. In the interim, restrict access to log files and consider rotating credentials that may have been exposed through logging.

Recommended fix High confidence

9.1.0.27, 9.2.1.20, or 9.4.0.11 (or any later version)

  1. 1. Identify the current PowerScale OneFS version using 'isi version' or through the web UI (Cluster Management > About)
  2. 2. Schedule a maintenance window for the upgrade (ensure adequate backup and cluster health)
  3. 3. Download the appropriate OneFS iso/image from Dell Support (support.dell.com) for the target fixed version
  4. 4. For single node clusters: Run 'isi upgrade' with the iso path, or use the WebUI (Cluster Management > Updates > Manual Update
  5. 5. For multi-node clusters: Ensure at least 2 nodes are operational; run 'isi upgrade' or use WebUI, the cluster will automatically balance
  6. 6. Verify upgrade completion with 'isi version' and check cluster health with 'isi cluster status'
Caveat Major OneFS upgrades may require cluster rebalance; verify compatibility with existing protocols and applications after upgrade

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

Fix this in Emc Powerscale Onefs Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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