CVE-2025-46423
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. A low privileged attacker with local access could potentially exploit this vulnerability to execute arbitrary 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 confidenceDell Unity storage systems versions 5.5 and prior contain an OS command injection vulnerability allowing a low-privileged local attacker to execute arbitrary commands with root privileges due to improper neutralization of special elements in OS command execution.
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.2.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
- 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.
-
Check Dell Unity Operating Environment versionAccess the Unisphere web interface and navigate to Settings > System > About, or use the CLI command 'uemcli -id /sys/general get' to retrieve the system versionAffected if The displayed version is earlier than 5.5.2.0 (for example, 5.5.1.x, 5.4.x, or any version in the 5.5 line prior to 5.5.2.0)
-
Verify version matches CVE affected rangeCompare your installed version number against the vulnerable range: any version below 5.5.2.0 including all 5.5.x versions and priorAffected if The version string shows a number less than 5.5.2.0 (for example, 5.5.0.0, 5.4.0.0, etc.)
-
Confirm low-privileged local account accessReview local user accounts on the Dell Unity system using Unisphere (Settings > Access > Management) or CLI: 'uemcli -id /auth/user show'Affected if Low-privileged local user accounts exist on the system, as these accounts can potentially exploit the command injection flaw
-
Check for command execution loggingReview system logs for unusual command execution events. Access logs via Unisphere (Monitoring > Logs) or export system logs for analysisAffected if Logs show unexpected or unauthorized command executions, particularly commands run by low-privileged users that indicate privilege escalation
The environment is affected if the Dell Unity Operating Environment version is below 5.5.2.0 and low-privileged local accounts have access to the system.
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.2.0
Apply vendor-supplied patches for Dell Unity to address the command injection flaw; restrict local access to trusted personnel and monitor for privilege escalation indicators.
Unity Operating Environment 5.5.2.0 or later
- 1. Back up the current Unity system configuration and data according to Dell backup procedures
- 2. Download Unity Operating Environment version 5.5.2.0 or later from Dell Support website (support.dell.com)
- 3. Review Dell Unity update documentation for your specific model to ensure compatibility
- 4. Apply the firmware/software update following Dell's recommended upgrade procedure
- 5. After update completes, verify the system is running version 5.5.2.0 or later
- 6. Validate that the command injection vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46423 — 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-46423 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