Unity Operating EnvironmentApplication · Dell

CVE-2022-29091

MEDIUM · 6.1 CVSS v3.1 Published 2022-05-26
Fix available
A fix is available. Upgrade to 5.2.0.0.5.173 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Unity, Dell UnityVSA, and Dell UnityXT versions prior to 5.2.0.0.5.173 contain a Reflected Cross-Site Scripting Vulnerability in Unisphere GUI. An Unauthenticated Remote Attacker could potentially exploit this vulnerability, leading to the execution of malicious HTML or JavaScript code in a victim user's web browser in the context of the vulnerable web application. Exploitation may lead to information disclosure, session theft, or client-side request forgery.

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 · high confidence

Dell Unity, UnityVSA, and UnityXT versions prior to 5.2.0.0.5.173 contain a reflected cross-site scripting (XSS) vulnerability in the Unisphere web GUI. An unauthenticated remote attacker can craft malicious URLs containing JavaScript payloads that, when clicked by a victim user, execute in the context of the vulnerable web application, potentially leading to session theft or information disclosure.

MitigationUpgrade Dell Unity, UnityVSA, or UnityXT systems to version 5.2.0.0.5.173 or later to obtain the vendor patch. Alternatively, disable or restrict access to the Unisphere GUI until patching can be completed.

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
Unity Operating EnvironmentApplication
Affected:< 5.2.0.0.5.173
Unity Xt Operating EnvironmentApplication
Affected:< 5.2.0.0.5.173
Unityvsa Operating EnvironmentApplication
Affected:< 5.2.0.0.5.173

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify the installed product
    Log into the system via SSH or console and run 'uemcli -noHeader /sys/general show' or check Unisphere login page footer for product name (Unity, UnityVSA, or UnityXT)
    Affected if Product is Dell Unity, UnityVSA, or UnityXT
  2. Check the installed version
    Log into Unisphere and navigate to Settings > General > About, or use CLI command 'uemcli -noHeader /sys/general show' to retrieve the OE version number
    Affected if Version number is lower than 5.2.0.0.5.173
  3. Confirm Unisphere web GUI is accessible
    Attempt to reach the Unisphere web interface via browser at https://<management-IP>/Unisphere, or verify the web service is running using 'service --status-all | grep -i unisphere' via CLI
    Affected if The Unisphere web GUI is enabled and reachable on the network

The environment is affected if the product is Dell Unity, UnityVSA, or UnityXT with an OE version below 5.2.0.0.5.173 and the Unisphere web GUI is currently enabled and 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 5.2.0.0.5.173 or later
Fixed in 5.2.0.0.5.173
Interim mitigation

Upgrade Dell Unity, UnityVSA, or UnityXT systems to version 5.2.0.0.5.173 or later to obtain the vendor patch. Alternatively, disable or restrict access to the Unisphere GUI until patching can be completed.

Recommended fix High confidence

5.2.0.0.5.173 or later

  1. Verify current Unity, UnityVSA, or UnityXT version via Unisphere GUI or CLI
  2. Review Dell Unity upgrade documentation and release notes for version 5.2.0.0.5.173
  3. Schedule maintenance window as upgrades require system downtime
  4. Backup current configuration and data
  5. Download Unity version 5.2.0.0.5.173 or later from Dell Support website
  6. Upload upgrade bundle via Unisphere or Service GUI
  7. Execute upgrade following Dell-provided procedures
  8. Verify system health and version post-upgrade
Caveat Review release notes for any configuration or compatibility changes between current version and 5.2.0.0.5.173

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

Fix this in Unity Operating Environment Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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