CVE-2025-36604
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 · uneditedDell Unity, version(s) 5.5 and prior, contain(s) an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to arbitrary command execution.
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 confidenceDell Unity storage systems versions 5.5 and prior contain an OS command injection vulnerability allowing unauthenticated remote attackers to execute arbitrary commands on the underlying operating system by injecting malicious commands through unsanitized input fields in the management interface.
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< 5.5.1.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Dell Unity storage systemAccess the storage array management interface (Unisphere) or use the 'uss' CLI command: 'uss list' or check the system banner during login to confirm the system is a Dell Unity storage arrayAffected if The target system is a Dell Unity storage array running Dell Unity Operating Environment
-
Check installed version via UnisphereLog into the Unisphere web interface and navigate to Settings > About, or use the 'uemcli -sys version' command from the service account to retrieve the exact Operating Environment version numberAffected if The displayed version is below 5.5.1.0 (for example, 5.4.x, 5.3.x, or any 5.5.x version prior to 5.5.1.0)
-
Check version via CLIConnect to the service CLI (SSH as root or service account) and run: 'version' or 'uemcli -sys version' to obtain the firmware/OS versionAffected if The reported version string shows a build prior to 5.5.1.0
-
Confirm management interface exposureReview firewall rules or network configuration to determine if UDP/TCP ports 443, 22, or other management ports used by Unisphere are accessible from untrusted networksAffected if Management interfaces (HTTP/HTTPS/SSH) are exposed to unauthenticated or untrusted network segments, enabling the unauthenticated attacker vector
A user is affected if they are running Dell Unity Operating Environment version 5.5.x prior to 5.5.1.0 (or any version below 5.5.1.0) with management interfaces accessible to untrusted networks, allowing unauthenticated remote command injection.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.5.1.0
Apply the vendor-provided security patch from Dell for Unity version 5.5 and prior; if no patch is immediately available, restrict network access to management interfaces using firewalls or VPNs and monitor for indicators of compromise.
Unity Operating Environment 5.5.1.0 or later
- Verify current Unity Operating Environment version via the management interface or CLI
- Review Dell Unity upgrade documentation and ensure backup procedures are in place
- Download Unity Operating Environment version 5.5.1.0 or later from Dell support portal (support.dell.com)
- Schedule maintenance window as upgrades may require system downtime
- Follow Dell's official upgrade procedure for Unity OE, typically via the Unisphere interface or CLI
- After upgrade, verify the system is running version 5.5.1.0 or later
- Confirm the vulnerability is remediated by checking the applied patches/versions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36604 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36604 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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