Unity Operating EnvironmentApplication · Dell

CVE-2023-43067

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 an XML External Entity injection vulnerability. An XXE attack could potentially exploit this vulnerability disclosing local files in the file system.

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 an XML External Entity (XXE) injection vulnerability. The flaw allows authenticated attackers to craft malicious XML requests that can read local files from the filesystem, potentially exposing sensitive configuration data, credentials, or other system files.

MitigationUpgrade Dell Unity to version 5.3 or later. If immediate patching is not possible, disable XML external entity processing in the application's XML parser configuration as a compensating control.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Unity storage system
    Identify if the target system is a Dell Unity, Unity Xt, or Unityvsa storage array by checking the system model, product name in the management interface, or via the Unity Unisphere web interface
    Affected if The system is a Dell Unity storage array of any type
  2. Locate the installed firmware version
    Access Unisphere management interface, navigate to Settings > About, or use the 'system' CLI command to retrieve the current Operating Environment version number
    Affected if Unable to determine the version from the system
  3. Compare version against affected range
    Check if the installed version is below 5.3.0.0.5.120 for Unity, Unity Xt, or Unityvsa variants
    Affected if Installed version is lower than 5.3.0.0.5.120
  4. Verify web API exposure
    Confirm whether the Unisphere REST API or XML-based management endpoints are accessible over the network on ports 443 or 8080
    Affected if XML management interfaces are exposed externally without proper access controls

The environment is affected if it runs a Dell Unity, Unity Xt, or Unityvsa system with Operating Environment version lower than 5.3.0.0.5.120 and has accessible XML management interfaces.

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. If immediate patching is not possible, disable XML external entity processing in the application's XML parser configuration as a compensating control.

Recommended fix High confidence

Unity Operating Environment 5.3.0.0.5.120 or later (including Unity Xt and Unityvsa)

  1. 1. Schedule a maintenance window for the Unity storage system upgrade
  2. 2. Back up all critical data and configuration settings before proceeding
  3. 3. Download the Unity Operating Environment version 5.3.0.0.5.120 or later from Dell Support (support.dell.com)
  4. 4. Access the Unity system via Unisphere or the Service GUI
  5. 5. Navigate to the firmware/software update section
  6. 6. Upload and apply the 5.3.0.0.5.120 (or later) Operating Environment update
  7. 7. Verify the upgrade completed successfully and the system is operational
  8. 8. Validate that the XXE vulnerability is no longer present by confirming the new firmware version
Caveat Storage array firmware upgrades require planned downtime and should be thoroughly tested in a non-production environment first; always review Dell Unity upgrade guide for compatibility requirements

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

Fix this in Unity Operating Environment Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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