dbcve.org
Unity Operating EnvironmentApplication · Dell

CVE-2023-43066

HIGH · 7.8 CVSS v3.1 Published 2023-10-23
Fix available
A fix is available. Upgrade to 5.3.0.0.5.120 or later.
See remediation →
80/100
Remediation priority · High
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 Unity prior to 5.3 contains a Restricted Shell Bypass vulnerability. This could allow an authenticated, local attacker to exploit this vulnerability by authenticating to the device CLI and issuing certain commands.

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 Unity storage systems prior to version 5.3 contain a restricted shell bypass vulnerability in the CLI. An authenticated local attacker with limited shell access can escape the restricted shell environment and execute commands outside their intended权限 boundaries.

MitigationUpgrade Dell Unity to version 5.3 or later to apply the security patch that addresses the restricted shell bypass.

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.3.0.0.5.120
Unity Xt Operating EnvironmentApplication
Affected:< 5.3.0.0.5.120
Unityvsa Operating EnvironmentApplication
Affected:< 5.3.0.0.5.120

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
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 checks

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

  1. Identify the Dell Unity product variant
    Run the command 'system show -product' or check the system name/model in the Unisphere management interface to determine if the system is Dell Unity, Unity Xt, or Unityvsa.
    Affected if The product is any of the three Unity variants (Unity, Unity Xt, Unityvsa)
  2. Check the installed Operating Environment version
    Execute 'version' or 'system version' in the CLI, or view the version in Unisphere under Settings > System > About. Note the full version string including the build number.
    Affected if The version is lower than 5.3.0.0.5.120 (for example, 5.2.x.x or 5.3.0.0.x where x is less than 5.120)
  3. Verify CLI service status
    Check if the service 'SMB' or 'SSH' is enabled by running 'service -v -name <servicename> status' or viewing services in Unisphere under Access > Management. Note that the CLI may be accessible via console or SSH.
    Affected if CLI access (SSH or console) is enabled and accessible to local users
  4. Confirm local user account existence
    Review local user accounts via 'user -list' in CLI or in Unisphere under Access > Users > Local Users. Identify any accounts with limited or restricted shell permissions.
    Affected if Local user accounts with restricted shell access exist in the system

You are affected if your Dell Unity, Unity Xt, or Unityvsa system runs a version earlier than 5.3.0.0.5.120 AND has CLI access enabled for local authenticated users.

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.3.0.0.5.120 or later
Fixed in 5.3.0.0.5.120
Interim mitigation

Upgrade Dell Unity to version 5.3 or later to apply the security patch that addresses the restricted shell bypass.

Recommended fix Moderate confidence

Unity Operating Environment 5.3.0.0.5.120 or later (Unity, Unity Xt, Unityvsa)

  1. 1. Back up current Unity system configuration and data
  2. 2. Download Unity Operating Environment version 5.3.0.0.5.120 or later from Dell support portal
  3. 3. Schedule a maintenance window as upgrade requires system downtime
  4. 4. Upload the upgrade package to the Unity system
  5. 5. Run the upgrade command via Unity CLI or management interface
  6. 6. Verify the upgrade completed successfully and system is operational
  7. 7. Confirm the version is 5.3.0.0.5.120 or later using 'system version' command
Caveat Upgrade may require downtime; test in non-production environment first; review Dell upgrade documentation for prerequisites

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-2023-43066 — 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-2023-43066 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