CVE-2022-45096
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 · uneditedDell PowerScale OneFS, 8.2.0 through 9.3.0, contain an User Interface Security Issue. An unauthenticated remote user could unintentionally lead an administrator to enable this vulnerability, leading to disclosure of information.
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 confidenceDell PowerScale OneFS versions 8.2.0 through 9.3.0 contain a UI security vulnerability where an unauthenticated remote attacker can manipulate an administrator into enabling a vulnerable configuration, leading to information disclosure. The CVSS 6.5 score indicates network-exploitable, low-privilege information exposure.
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>= 9.1.0.0, < 9.1.0.25>= 9.2.1.0, < 9.2.1.18>= 9.4.0.0, < 9.4.0.9CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed PowerScale OneFS versionRun 'isi version' or check the OneFS web UI footer for the version numberAffected if The installed version falls within 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
-
Identify the OneFS UI session configuration settingsAccess the PowerScale OneFS web administration UI, navigate to Session settings or Security settings under the administrative interfaceAffected if A session configuration allows unauthenticated users to influence or modify security-related settings
-
Check for external UI redirect or manipulation vectorsReview the OneFS UI configuration for settings that control URL redirection, external resource loading, or user-initiated configuration changes from unauthenticated contextsAffected if The UI permits unauthenticated attackers to trigger actions that modify security configurations through social engineering of administrators
-
Audit recent UI configuration changesReview OneFS audit logs or system logs for any recent changes to UI security settings, particularly those related to session management or information exposureAffected if Audit logs show unexpected or unauthorized modifications to UI security configurations
You are affected if your PowerScale OneFS version is 9.1.0.0-9.1.0.24, 9.2.1.0-9.2.1.17, or 9.4.0.0-9.4.0.8 AND your administrative UI allows unauthenticated users to manipulate security settings that can lead to information disclosure.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.1.0.259.2.1.189.4.0.9
Upgrade to a patched Dell PowerScale OneFS version beyond 9.3.0, and review administrator UI session configurations to prevent unintended security setting modifications by unauthenticated users.
Upgrade to OneFS 9.1.0.25, 9.2.1.18, 9.4.0.9 or later (choose the appropriate branch for your deployment)
- 1. Back up all critical data and cluster configuration before initiating any upgrade
- 2. Verify current OneFS version by running 'isi version' or checking the web UI
- 3. Download the appropriate fixed OneFS ISO image (9.1.0.25, 9.2.1.18, or 9.4.0.9 or later) from Dell Support portal at www.dell.com
- 4. Upload the ISO to the cluster using 'isi imaging' or the web UI
- 5. Initiate the upgrade following Dell PowerScale OneFS upgrade documentation (typically isi upgrade start)
- 6. Monitor the upgrade progress and allow sufficient time for completion
- 7. After upgrade, verify the new version with 'isi version' and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2022-45096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45096 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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