CVE-2022-46679
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.x, 9.0.0.x - 9.4.0.x, contain an insufficient resource pool vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability, leading to denial of service.
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 contains an insufficient resource pool vulnerability where the system fails to properly restrict or allocate resources (such as memory, connections, or handles) to handle incoming requests. A remote unauthenticated attacker can exploit this by exhausting available resources, causing the system to become unavailable to legitimate users.
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.26>= 9.2.1.0, < 9.2.1.19>= 9.4.0.0, < 9.4.0.10CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PowerScale OneFS versionRun the command to display the OneFS version (e.g., isi version via CLI or check the web administration UI system information page)Affected if The installed version falls within these ranges: 9.1.0.0 through 9.1.0.25, 9.2.1.0 through 9.2.1.18, or 9.4.0.0 through 9.4.0.9 (any version >= 9.1.0.0 and < 9.1.0.26, >= 9.2.1.0 and < 9.2.1.19, or >= 9.4.0.0 and < 9.4.0.10)
-
Verify available patches are appliedConsult the OneFS patch management interface or release notes to confirm whether all available security updates have been installedAffected if The system is running an affected version and has not had the corresponding security patch applied
A system is affected if it runs PowerScale OneFS version 9.1.0.x before 9.1.0.26, 9.2.1.x before 9.2.1.19, or 9.4.0.x before 9.4.0.10 and is reachable by remote unauthenticated network attackers.
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.269.2.1.199.4.0.10
Apply the vendor-provided security update or patch for Dell PowerScale OneFS to address the resource pool vulnerability. If immediate patching is not possible, implement network-level access controls to limit exposure to untrusted networks.
Upgrade to 9.1.0.26, 9.2.1.19, or 9.4.0.10 depending on current version branch (minimum fixed version in each respective branch)
- Identify the current OneFS version running on the PowerScale cluster (ISI version -q or through the web UI under Cluster > Overview)
- Determine which version branch the cluster is currently on (9.1.x, 9.2.x, or 9.4.x)
- Plan a maintenance window as OneFS upgrades require cluster downtime
- Download the appropriate upgrade ISO from Dell Support (www.dell.com/support) - choose 9.1.0.26 for 9.1.x branches, 9.2.1.19 for 9.2.x branches, or 9.4.0.10 for 9.4.x branches
- Review the OneFS upgrade guide and release notes for pre-upgrade checks and prerequisites
- Perform a pre-upgrade assessment and backup cluster configuration
- Mount the upgrade ISO and initiate the upgrade via 'isi upgrade start' CLI command or through the WebUI
- Allow the upgrade to complete; the cluster will reboot as part of the process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46679 — 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-46679 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