dbcve.org
Unity Operating EnvironmentApplication · Dell

CVE-2023-43074

HIGH · 7.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 →
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 Unity 5.3 contain(s) an Arbitrary File Creation vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability by crafting arbitrary files through a request to the server.

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 5.3 contains an arbitrary file creation vulnerability that allows a remote unauthenticated attacker to write arbitrary files to the server through crafted requests. This could enable code execution, data manipulation, or denial of service depending on file location and content.

MitigationApply the vendor-supplied patch or update to Dell Unity 5.3. If immediate patching is not possible, consider network segmentation to limit exposure and monitor for suspicious file creation activity.

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
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. Identify Dell Unity product variant
    Determine which Dell Unity product is deployed: Unity, Unity Xt, or Unityvsa (virtual appliance). This is typically visible in the system management interface or product documentation.
    Affected if Any of the three variants (Unity, Unity Xt, or Unityvsa) is in use.
  2. Check installed software version
    Locate the installed version of the Dell Unity Operating Environment through the Unisphere management interface, system diagnostics, or CLI (run 'version' or 'system show version' command).
    Affected if The installed version is below 5.3.0.0.5.120.
  3. Verify version falls within vulnerable range
    Compare your installed version number against the affected range: versions < 5.3.0.0.5.120 for all three product variants.
    Affected if Your version is 5.3.0.0.5.119 or lower, or any 5.2.x or earlier release.
  4. Assess network exposure
    Determine if the Unisphere management interface or REST API endpoints are directly accessible from untrusted networks. Check firewall rules and network segmentation around the storage system.
    Affected if The management interface is exposed to untrusted networks without proper access controls.

You are affected if your Dell Unity system runs any variant (Unity, Unity Xt, or Unityvsa) with a version below 5.3.0.0.5.120 and has its management interface network-accessible to potential attackers.

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

Apply the vendor-supplied patch or update to Dell Unity 5.3. If immediate patching is not possible, consider network segmentation to limit exposure and monitor for suspicious file creation activity.

Recommended fix Moderate confidence

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

  1. 1. Identify the current Unity Operating Environment version installed on the system
  2. 2. Navigate to Dell support site (www.dell.com) and search for Dell Unity security patch or update related to CVE-2023-43074
  3. 3. Download the Unity Operating Environment version 5.3.0.0.5.120 or later
  4. 4. Review Dell Unity upgrade documentation for your specific product (Unity, Unity Xt, or Unityvsa)
  5. 5. Schedule a maintenance window as upgrades may require system downtime
  6. 6. Perform backup of critical data following Dell best practices
  7. 7. Apply the upgrade following Dell's official upgrade procedure for your Unity platform
  8. 8. Verify the installed version is 5.3.0.0.5.120 or higher after upgrade
Caveat Review Dell Unity 5.3 release notes for any compatibility considerations or known issues before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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