dbcve.org
Emc Powerstore 500t FirmwareOperating system · Dell

CVE-2022-22555

MEDIUM · 6.7 CVSS v3.1 Published 2022-07-21
Fix available
A fix is available. Upgrade to 3.0.0.0-1732745 or later.
See remediation →
69/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 EMC PowerStore, contains an OS command injection Vulnerability. A locally authenticated attacker could potentially exploit this vulnerability, leading to the execution of arbitrary OS commands on the PowerStore underlying OS, with the privileges of the vulnerable application. Exploitation may lead to an elevation of privilege.

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 EMC PowerStore contains an OS command injection vulnerability that allows a locally authenticated attacker to execute arbitrary OS commands on the underlying operating system with the privileges of the vulnerable application, potentially leading to elevation of privilege.

MitigationApply the vendor-provided security patch or firmware update for PowerStore immediately, and restrict local access to trusted, least-privilege accounts to reduce the attack surface.

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 Powerstore 500t FirmwareOperating system
Affected:< 3.0.0.0-1732745
Emc Powerstore 1200t FirmwareOperating system
Affected:< 3.0.0.0-1732745
Emc Powerstore 3200t FirmwareOperating system
Affected:< 3.0.0.0-1732745
Emc Powerstore 5200t FirmwareOperating system
Affected:< 3.0.0.0-1732745
Emc Powerstore 9200t FirmwareOperating system
Affected:< 3.0.0.0-1732745

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your PowerStore appliance model
    Access the PowerStore management interface or use the support CLI to query the system for the exact model number (500t, 1200t, 3200t, 5200t, or 9200t)
    Affected if The model is one of the five affected PowerStore variants listed in the CVE (500t, 1200t, 3200t, 5200t, or 9200t)
  2. Determine the installed firmware version
    Using the PowerStore UI or command line interface, retrieve the current firmware version. Typically found in Settings > Support > About, or via the 'storage system show' command in the service CLI
    Affected if You cannot determine the firmware version or the system responds with a version that is not readable in the format shown below
  3. Compare firmware version against the vulnerable range
    Check if your installed firmware version is lower than 3.0.0.0-1732745. The format is major.minor.patch-buildnumber. Compare numerically: any version below 3.0.0.0, or version 3.0.0.0 with build number below 1732745, is affected
    Affected if The installed firmware version is less than 3.0.0.0-1732745 (for example, 2.7.x.x, 2.5.x.x, or 3.0.0.0-1720000)
  4. Verify local authentication is possible
    Determine whether local user accounts exist and can log in to the PowerStore system. Check for locally-defined service accounts or local administrator access
    Affected if Local user authentication is enabled and functional on the appliance (the vulnerability can be exploited by any locally authenticated user)

Your environment is affected if you run a PowerStore 500t, 1200t, 3200t, 5200t, or 9200t with firmware version below 3.0.0.0-1732745 and local user authentication is available.

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 3.0.0.0-1732745 or later
Fixed in 3.0.0.0-1732745
Interim mitigation

Apply the vendor-provided security patch or firmware update for PowerStore immediately, and restrict local access to trusted, least-privilege accounts to reduce the attack surface.

Recommended fix High confidence

Firmware version 3.0.0.0-1732745 or later

  1. Verify the current firmware version by accessing the PowerStore management interface or running the 'esrs_cli get version' command
  2. Download the fixed firmware version 3.0.0.0-1732745 or later from the Dell EMC support portal (www.dell.com/support)
  3. Review the PowerStore firmware upgrade guide and ensure all prerequisites are met, including backup of critical data
  4. Initiate the firmware upgrade through the PowerStore UI or CLI using the 'firmware update' command with the downloaded firmware file
  5. Monitor the upgrade process and verify completion status
  6. After upgrade, confirm the new firmware version is 3.0.0.0-1732745 or higher using the management interface
  7. Validate that the OS command injection vulnerability is resolved by verifying the security patch is applied
Caveat Firmware upgrades may require downtime and should be scheduled during maintenance windows; test thoroughly in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Emc Powerstore 500t Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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