dbcve.org
Unity Operating EnvironmentApplication · Dell

CVE-2025-36607

HIGH · 7.8 CVSS v3.1 Published 2025-08-04
Fix available
A fix is available. Upgrade to 5.5.1.0 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, version(s) 5.5 and prior, contain(s) an OS Command Injection Vulnerability in its svc_nas utility. An authenticated attacker could potentially exploit this vulnerability, escaping the restricted shell and execute arbitrary operating system commands with root privileges.

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 storage systems version 5.5 and prior contain an OS command injection vulnerability in the svc_nas utility. An authenticated attacker can exploit this flaw to escape the restricted shell environment and execute arbitrary operating system commands with root privileges.

MitigationApply the vendor-supplied patch or upgrade Dell Unity to a version beyond 5.5. Until patching is possible, strictly limit access to authenticated sessions and monitor for indicators of compromise involving the svc_nas utility.

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.5.1.0

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 installed Dell Unity OE version
    Access the Dell Unity Unisphere management interface or use the uemcli command line tool to retrieve the system version. Run 'uemcli -d [array_ip] show system' or check the GUI under Settings > System > About.
    Affected if The installed version is 5.5.0.x, 5.4.x, or any version prior to 5.5.1.0 (meaning the version falls below 5.5.1.0)
  2. Locate the svc_nas utility on the system
    Check for the presence of the svc_nas binary or script within the Dell Unity filesystem. On the service console (if accessible), look for svc_nas under /svc or similar service directories, or query the system for registered service utilities.
    Affected if The svc_nas utility exists and is accessible to authenticated users on the system
  3. Verify authenticated user access to svc_nas functionality
    Review the user roles and permissions configured in Unisphere or via uemcli. Determine which authenticated user accounts have permissions to invoke or interact with the svc_nas utility.
    Affected if Any authenticated non-admin or service account can access or invoke the svc_nas utility
  4. Review audit and system logs for svc_nas command anomalies
    Examine Dell Unity logs for any suspicious invocations of svc_nas that include unexpected arguments, shell metacharacters, or patterns indicative of command injection attempts. Use the Log Analyzer in Unisphere or access raw log files.
    Affected if Logs show svc_nas being called with unusual or malformed arguments that suggest command injection or restricted shell escape attempts

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.5.1.0 or later
Fixed in 5.5.1.0
Interim mitigation

Apply the vendor-supplied patch or upgrade Dell Unity to a version beyond 5.5. Until patching is possible, strictly limit access to authenticated sessions and monitor for indicators of compromise involving the svc_nas utility.

Recommended fix Moderate confidence

Unity Operating Environment 5.5.1.0 or later

  1. Identify current Unity Operating Environment version using the Unisphere web interface or CLI
  2. Review Dell Unity upgrade documentation for 5.5.1.0 or later release
  3. Create a complete backup of all critical data and configuration
  4. Schedule a maintenance window for the upgrade procedure
  5. Download the Unity OE 5.5.1.0 or later update package from Dell Support
  6. Apply the Unity Operating Environment upgrade following Dell's documented procedure
  7. Verify the upgrade completed successfully and the system is running version 5.5.1.0 or later
  8. Confirm the svc_nas utility vulnerability is no longer present
Caveat Unity OE upgrades may require downtime and should be performed according to Dell's migration/upgrade compatibility matrix; verify all attached systems are compatible

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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