dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2023-22573

MEDIUM · 5.5 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 →
57/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 9.0.0.x-9.4.0.x contain an insertion of sensitive information into log file vulnerability in cloudpool. A low privileged local attacker could potentially exploit this vulnerability, leading to sensitive information disclosure.

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 9.0.0.x through 9.4.0.x contain a vulnerability in the cloudpool component where sensitive information is written to log files. A low-privileged local user with basic system access can exploit this to view the improperly logged sensitive data, leading to information disclosure.

MitigationUpgrade to a patched version of Dell PowerScale OneFS beyond 9.4.0.x, and review existing cloudpool logs to identify and remediate any exposed sensitive information.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 your PowerScale OneFS version
    Run the 'isi version' command or check the system information in the OneFS web interface under Cluster > Overview
    Affected if The installed version falls within 9.1.0.0 through 9.1.0.26, 9.2.1.0 through 9.2.1.19, or 9.4.0.0 through 9.4.0.10
  2. Identify if cloudpool is configured
    Check for cloudpool configuration using 'isi cloudpool list' or via the OneFS web interface under Cloud > CloudPools
    Affected if Cloudpool is enabled and has pools configured on the system
  3. Locate cloudpool log files
    Navigate to the log directory for cloudpool services, typically found under /var/log/isi_cloudpool/ or check the OneFS log directory structure for cloudpool-related log files
    Affected if Cloudpool log files exist on the system
  4. Inspect cloudpool logs for sensitive data
    Search cloudpool log files for patterns that may indicate exposed credentials, API keys, tokens, or other sensitive information that should not be logged (use grep or a log analysis tool)
    Affected if Log files contain any improperly logged sensitive information such as passwords, secrets, or authentication tokens

You are affected if your OneFS version is within the vulnerable ranges AND cloudpool is configured, as the combination enables a low-privileged user to access sensitive data in cloudpool logs.

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

Upgrade to a patched version of Dell PowerScale OneFS beyond 9.4.0.x, and review existing cloudpool logs to identify and remediate any exposed sensitive information.

Recommended fix High confidence

Upgrade to 9.1.0.27+ (9.1.x), 9.2.1.20+ (9.2.x), or 9.4.0.11+ (9.4.x) - choose the latest available stable release in your branch

  1. 1. Identify the current PowerScale OneFS version using 'isi version' or through the WebUI under Cluster > Overview
  2. 2. Based on current version, upgrade to a fixed release: For 9.1.0.x branch, upgrade to 9.1.0.27 or later; For 9.2.1.x branch, upgrade to 9.2.1.20 or later; For 9.4.0.x branch, upgrade to 9.4.0.11 or later
  3. 3. Download the upgrade iso from Dell Support (www.dell.com/support) for the appropriate fixed version
  4. 4. Apply the upgrade using 'isi upgrade' command or through the WebUI under Cluster > Updates
  5. 5. After upgrade, verify the version matches the expected fixed release using 'isi version'
  6. 6. Review cloudpool logs to confirm sensitive information is no longer being written to log files
Caveat Standard OneFS upgrade considerations apply - review release notes for any configuration or compatibility notices before upgrading

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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