Unisphere For Powermax Virtual ApplianceApplication · Dell

CVE-2022-34363

HIGH · 7.5 CVSS v3.1 Published 2026-05-22
Fix available
A fix is available. Upgrade to 10.0.0.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Unisphere for PowerMax vApp version prior to 10.0.0.2, contains an authorization bypass vulnerability in the  Unisphere for VMAX application running in vApp

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 Unisphere for PowerMax vApp versions prior to 10.0.0.2 contain an authorization bypass vulnerability in the Unisphere for VMAX application running within the vApp. This allows unauthenticated or unauthorized attackers to bypass access controls and potentially gain unauthorized access to the storage management interface.

MitigationUpgrade Dell Unisphere for PowerMax vApp to version 10.0.0.2 or later to remediate the authorization bypass vulnerability. Ensure the upgrade is performed during a scheduled maintenance window with prior configuration backups.

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
Unisphere For Powermax Virtual ApplianceApplication
Affected:< 10.0.0.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Confirm Dell Unisphere for PowerMax vApp deployment
    Check your VMware inventory or virtualization infrastructure for a virtual appliance named 'Dell Unisphere for PowerMax' or 'Unisphere for VMAX'. Look in vCenter inventory, VM templates, or your infrastructure documentation.
    Affected if The virtual appliance is present in the environment
  2. Locate the Unisphere web interface access point
    Identify the IP address or hostname used to access the Unisphere for PowerMax management interface. This is typically exposed on port 8443 or 443 via the vApp.
    Affected if The Unisphere web interface is network-accessible
  3. Determine the installed Unisphere version
    Log into the Unisphere for PowerMax web interface and navigate to the 'About' or 'Support' page to view the software version. Alternatively, access the vApp VM console and check the welcome screen or system information for the version number.
    Affected if The displayed version is any build prior to 10.0.0.2 (for example, 10.0.0.0, 10.0.0.1, 9.2.x, or earlier)
  4. Verify the Unisphere for VMAX application component
    Within the Unisphere interface, confirm the 'Unisphere for VMAX' or 'Unisphere for PowerMax' application management console is accessible and operational.
    Affected if The Unisphere for VMAX management interface is accessible

A user is affected if the Dell Unisphere for PowerMax vApp is deployed with any version prior to 10.0.0.2 and the Unisphere for VMAX interface is network-accessible.

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

Upgrade Dell Unisphere for PowerMax vApp to version 10.0.0.2 or later to remediate the authorization bypass vulnerability. Ensure the upgrade is performed during a scheduled maintenance window with prior configuration backups.

Recommended fix Moderate confidence

Upgrade to Unisphere for PowerMax Virtual Appliance version 10.0.0.2 or later

  1. Obtain the fixed version 10.0.0.2 or later from Dell's support portal
  2. Review Dell's official upgrade documentation for Unisphere for PowerMax Virtual Appliance
  3. Perform a backup of the current vApp configuration before upgrading
  4. Execute the upgrade following Dell's documented upgrade procedure
  5. Verify the upgrade was successful by checking the Unisphere version
Caveat Review Dell's release notes for any configuration or compatibility changes in version 10.0.0.2

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

Fix this in Unisphere For Powermax Virtual Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34363 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