dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2022-31238

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-22
Fix available
A fix is available. Upgrade to after 9.4.0.2 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, versions 9.0.0 up to and including 9.1.0.19, 9.2.1.12, 9.3.0.6, and 9.4.0.2, contain a process invoked with sensitive information vulnerability. A CLI user may potentially exploit this vulnerability, leading to 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 contains an information disclosure vulnerability where a CLI user may be able to exploit a process that is invoked with sensitive information. This could allow a local CLI user to gain access to sensitive data that should not be exposed to them.

MitigationUpgrade Dell PowerScale OneFS to a version beyond the affected releases (9.1.0.19, 9.2.1.12, 9.3.0.6, 9.4.0.2) or apply the vendor-supplied patch if available.

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.19>= 9.2.1.0, <= 9.2.1.12>= 9.3.0.0, <= 9.3.0.6>= 9.4.0.0, <= 9.4.0.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
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 PowerScale OneFS version
    Run the CLI command to display the OneFS version, typically `isi version` or `isi --version` via SSH to the cluster
    Affected if The reported version falls within any of these ranges: 9.1.0.0-9.1.0.19, 9.2.1.0-9.2.1.12, 9.3.0.0-9.3.0.6, or 9.4.0.0-9.4.0.2
  2. Verify CLI access exists
    Confirm that SSH or console CLI access is enabled on the PowerScale node. Check via the management interface or by attempting an SSH connection to the cluster
    Affected if CLI access is permitted and a local CLI user account exists on the system
  3. Identify sensitive process execution
    Review system logs or process arguments for any scripts or commands that may handle sensitive data (such as credential files, keys, or configuration files containing secrets)
    Affected if Sensitive information is passed as command-line arguments to any processes invoked by the CLI, and those processes can be inspected by a local CLI user

The system is affected if the installed PowerScale OneFS version matches one of the affected ranges AND CLI user access is available, allowing inspection of sensitive data passed to processes.

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.4.0.2
Interim mitigation

Upgrade Dell PowerScale OneFS to a version beyond the affected releases (9.1.0.19, 9.2.1.12, 9.3.0.6, 9.4.0.2) or apply the vendor-supplied patch if available.

Recommended fix Moderate confidence

Upgrade to 9.1.0.20+ (for 9.1.x), 9.2.1.13+ (for 9.2.1.x), 9.3.0.7+ (for 9.3.0.x), or 9.4.0.3+ (for 9.4.0.x)

  1. 1. Identify the current PowerScale OneFS version by running 'isi get version' or checking the web UI.
  2. 2. Based on your current version line, plan upgrade to the first fixed release: For 9.1.x line upgrade to 9.1.0.20 or later; For 9.2.1.x upgrade to 9.2.1.13 or later; For 9.3.0.x upgrade to 9.3.0.7 or later; For 9.4.0.x upgrade to 9.4.0.3 or later.
  3. 3. Review Dell PowerScale OneFS upgrade documentation and release notes for the target version.
  4. 4. Create a backup or snapshot of the cluster data as a precaution before upgrading.
  5. 5. Schedule a maintenance window as upgrades require cluster downtime.
  6. 6. Download the upgrade iso/image from Dell Support (www.dell.com/support) for the appropriate fixed version.
  7. 7. Run the upgrade using 'isi upgrade' command or through the OneFS web interface.
  8. 8. After upgrade completes, verify the new version with 'isi get version' and confirm the CVE is resolved.
Caveat Standard OneFS upgrade may require cluster downtime; review release notes for any known issues or configuration changes in the target version

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-31238 — 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-31238 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