CVE-2022-26868
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 EMC PowerStore versions 2.0.0.x, 2.0.1.x, and 2.1.0.x are vulnerable to a command injection flaw. An authenticated attacker could potentially exploit this vulnerability, leading to the execution of arbitrary OS commands on the application's underlying OS, with the privileges of the vulnerable application. Exploitation may lead to a system takeover by an attacker.
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 EMC PowerStore versions 2.0.0.x, 2.0.1.x, and 2.1.0.x contain a command injection vulnerability allowing authenticated attackers to execute arbitrary OS commands with the application's privileges, potentially leading to complete system compromise.
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>= 2.0.0.0, < 2.1.1.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 PowerStore OS versionAccess the PowerStore management interface or use the command line tool 'storagesystem' with the '--version' flag to retrieve the installed PowerStoreos version.Affected if The installed version falls within the range >= 2.0.0.0 and < 2.1.1.0.
-
Confirm administrative authentication is enabledVerify that the PowerStore administrative interface (GUI, API, or CLI) is accessible and that user authentication is configured. Check the 'admin' or equivalent privileged user account status.Affected if Remote or local administrative authentication is active, providing attackers a potential vector to reach the vulnerable command injection point.
-
Review access to management interfacesInspect network accessible management endpoints (HTTPS port 443, API endpoints) to determine if they are exposed to untrusted networks. Use 'networkdiag' or view firewall rules via the management UI.Affected if The PowerStore management interfaces are reachable from networks outside the trusted administrative zone.
-
Audit privileged user accountsReview the list of configured administrative users in PowerStore via the 'user' command or management GUI. Check for any unauthorized or unexpected accounts.Affected if Unexpected or unauthorized accounts exist with administrative privileges, indicating potential compromise or misuse.
A system is affected if it runs PowerStoreos version 2.0.0.0 through 2.1.0.x and has accessible administrative interfaces that could allow an authenticated attacker to inject commands.
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 · scoped2.1.1.0
Apply the vendor-supplied patch or upgrade to a non-vulnerable version of PowerStore. If immediate patching is not possible, restrict administrative access to trusted personnel only and monitor for indicators of compromise.
PowerStore OS 2.1.1.0 or later
- Identify the current PowerStore OS version using the PowerStore management interface or CLI
- Schedule a maintenance window for the upgrade process
- Back up all critical data and configurations according to Dell best practices
- Download the PowerStore OS version 2.1.1.0 or later from Dell Support (support.dell.com)
- Apply the upgrade following Dell PowerStore upgrade documentation, typically via the PowerStore UI or CLI
- Verify the upgrade was successful and the version shows 2.1.1.0 or later
- Validate that the command injection vulnerability is no longer present
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-26868 — 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-26868 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