CVE-2025-24379
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.4 and prior, contain(s) an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Command execution and Elevation of 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 · moderate confidenceDell Unity storage systems version 5.4 and prior contain an OS Command Injection vulnerability. A low-privileged user with local system access can inject malicious OS commands, potentially achieving arbitrary command execution and privilege escalation to elevated system privileges.
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.0.0.5.259CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Dell Unity versionAccess the Unity Unisphere web interface and navigate to Settings > Support > System Information, or use the 'uemcli -sys' command line tool to retrieve the system versionAffected if The displayed version is 5.4.x or earlier, or any version below 5.5.0.0.5.259
-
Verify Unity OE version via CLIConnect to the Unity service system via SSH and run 'version' or 'uemcli -sys -detail' to confirm the exact Operating Environment version numberAffected if The version string is less than 5.5.0.0.5.259
-
Check local user account configurationIn Unisphere, navigate to Access > Management > Local Users to review all locally defined user accounts and their assigned rolesAffected if There are user accounts beyond the designated administrator accounts, or accounts with low-privileged roles that have local system access
-
Review audit logs for suspicious commandsIn Unisphere, go to Access > Security > Audit Log and search for events involving command execution or unusual administrative actions from standard user accountsAffected if Audit logs show command injection attempts or unexpected command executions from low-privileged sessions
You are affected if your Dell Unity Operating Environment version is below 5.5.0.0.5.259 and you have low-privileged local user accounts with system access.
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.0.0.5.259
Apply Dell-provided security patches for Unity version 5.4 and prior; as an interim measure, restrict local system access to only trusted administrators and minimize the attack surface by disabling unnecessary services.
Unity Operating Environment version 5.5.0.0.5.259 or later
- 1. Verify current Unity Operating Environment version through Unity Unisphere or CLI (run 'uemcli -sys version' or check via Unisphere System > Settings > General)
- 2. Schedule a maintenance window as enterprise storage upgrades typically require system downtime
- 3. Download the Unity Operating Environment update from Dell Support (support.dell.com) - look for version 5.5.0.0.5.259 or later
- 4. Back up all critical data and configuration (VMware RDM LUNs, NAS exports, database exports)
- 5. Follow Dell Unity upgrade procedure: upload the update bundle via Unisphere (Settings > Updates > Upload)
- 6. Install the update: go to Unisphere Settings > Updates > Install, select the uploaded bundle
- 7. Verify the upgrade completed successfully and system is operational
- 8. Confirm the new version is 5.5.0.0.5.259 or higher via 'uemcli -sys version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-24379 — 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-24379 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