CVE-2024-0167
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, versions prior to 5.4, contains an OS Command Injection Vulnerability in the svc_topstats utility. An authenticated attacker could potentially exploit this vulnerability, leading to the ability to overwrite arbitrary files on the file system 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 prior to 5.4 contain an OS command injection vulnerability in the svc_topstats utility. An authenticated attacker can exploit this flaw to overwrite arbitrary files on the filesystem with root 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.4.0.0.5.094CVSS 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.
-
Determine the Dell Unity Operating Environment versionAccess the Unity management interface (Unisphere) or use the CLI command 'system -version' or 'uinventory -system' to retrieve the installed OS versionAffected if The displayed version is below 5.4.0.0.5.094
-
Confirm the svc_topstats utility is present and accessibleLocate and verify the svc_topstats utility exists in the system bin or service directory, typically accessible via CLI or administrative interfaceAffected if The svc_topstats utility is found and accessible to authenticated users
-
Verify administrative access to the systemReview user accounts and authentication methods that have access to the Unity administrative interfaces where svc_topstats can be invokedAffected if Any authenticated administrative user account can access the svc_topstats utility interface
-
Check for recent unauthorized file modificationsReview system audit logs or file integrity monitoring alerts for unexpected file writes or modifications, particularly in system directoriesAffected if Any unexpected file modifications are found that coincide with svc_topstats utility usage by unauthorized accounts
The environment is affected if the Dell Unity Operating Environment version is below 5.4.0.0.5.094 AND the svc_topstats utility is accessible to authenticated users on 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.
From vendor data5.4.0.0.5.094
Upgrade Dell Unity systems to version 5.4 or later to remediate this vulnerability. Until patched, strictly limit access to authenticated administrative interfaces and monitor for any anomalous activity involving the svc_topstats utility.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0167 — 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-2024-0167 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