dbcve.org
Emc Powerscale OnefsOperating system · Dell

CVE-2022-45098

MEDIUM · 5.5 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 9.1.0.25 / 9.2.1.18 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 a cleartext storage of sensitive information vulnerability in S3 component. An authenticated local attacker could 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 versions 9.0.0.x through 9.4.0.x contain a cleartext storage vulnerability in the S3 component, where sensitive information is stored without encryption. An authenticated local attacker with access to the system could read this unencrypted sensitive data, leading to information disclosure.

MitigationApply the vendor patch from Dell to remediate this vulnerability. Until the patch is applied, limit local access to trusted authenticated users only and monitor for unauthorized access to S3-related storage locations.

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.25>= 9.2.1.0, < 9.2.1.18>= 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
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. Identify the installed PowerScale OneFS version
    Run 'isi version' or check the system information in the OneFS web administration interface under Cluster > Overview
    Affected if The version falls within these ranges: 9.1.0.0 through 9.1.0.24, 9.2.1.0 through 9.2.1.17, or 9.4.0.0 through 9.4.0.8
  2. Verify if the S3 protocol is enabled
    Check the S3 service status via 'isi services -a' or navigate to Protocols > S3 in the OneFS web interface to confirm S3 is running
    Affected if S3 protocol is actively enabled and running on the cluster
  3. Locate S3 configuration and data directories
    Inspect the /ifs directory structure, specifically looking under /ifs/.ifs or /var/local/ for S3-related subdirectories such as s3, s3config, or bucket data stores
    Affected if S3 buckets or configuration files exist in the storage cluster
  4. Check file permissions on S3 storage locations
    Use 'ls -la' on identified S3 directories and examine ownership and read permissions, particularly for files that may contain credentials, keys, or sensitive configuration data
    Affected if Untrusted local authenticated users have read access to S3-related directories or configuration files

The system is affected if PowerScale OneFS version is within the vulnerable ranges AND the S3 protocol is enabled, allowing a local authenticated attacker to read unencrypted sensitive data from S3 storage locations.

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.25 / 9.2.1.18 / 9.4.0.9 or later
Fixed in 9.1.0.259.2.1.189.4.0.9
Interim mitigation

Apply the vendor patch from Dell to remediate this vulnerability. Until the patch is applied, limit local access to trusted authenticated users only and monitor for unauthorized access to S3-related storage locations.

Recommended fix Moderate confidence

OneFS 9.1.0.25+ (for 9.1.x), 9.2.1.18+ (for 9.2.x), or 9.4.0.9+ (for 9.4.x)

  1. 1. Identify the current OneFS version running on the PowerScale cluster using 'isi version' or through the web admin interface
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release
  3. 3. For 9.1.0.x versions: Upgrade to OneFS 9.1.0.25 or later
  4. 4. For 9.2.1.x versions: Upgrade to OneFS 9.2.1.18 or later
  5. 5. For 9.4.0.x versions: Upgrade to OneFS 9.4.0.9 or later
  6. 6. Before upgrading, review OneFS upgrade prerequisites and create a cluster snapshot or backup
  7. 7. Follow Dell PowerScale OneFS upgrade procedure documented in the OneFS administration guide
  8. 8. After upgrade, verify the S3 component is functioning correctly
Caveat Standard OneFS upgrade considerations apply - review release notes for any feature changes or migration requirements

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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