CVE-2025-22473
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 SmartFabric OS10 Software, version(s) 10.5.4.x, 10.5.5.x, 10.5.6.x, 10.6.0.x, contain(s) an Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Code 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 · moderate confidenceDell SmartFabric OS10 versions 10.5.4.x through 10.6.0.x contain a command injection vulnerability where improper neutralization of special elements in input handling allows a low-privileged local attacker to execute arbitrary code on the affected system.
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>= 10.5.4.0, < 10.5.4.14>= 10.5.5.0, < 10.5.5.13>= 10.5.6.0, < 10.5.6.8>= 10.6.0.0, < 10.6.0.2CVSS 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 OS10 versionRun 'show version' or 'version' command in the OS10 CLI to retrieve the installed firmware versionAffected if The displayed version falls within any of these ranges: 10.5.4.0 to 10.5.4.13, 10.5.5.0 to 10.5.5.12, 10.5.6.0 to 10.5.6.7, or 10.6.0.0 to 10.6.0.1
-
Identify local user accountsRun 'show users' or 'show running-configuration | include username' to list configured local user accounts on the systemAffected if Multiple local user accounts exist with varying privilege levels, particularly if any non-administrator accounts have shell or exec access
-
Check for untrusted local accessReview physical access controls and console/SSH access policies. Inspect 'show access-list' or 'show ip access-list' to examine permitted access methodsAffected if The system allows local console access or SSH connections from untrusted users or networks
-
Audit input-handling interfacesExamine which CLI commands or APIs accept user-supplied parameters. Look for any custom scripts, aliases, or external integration points using 'show running-configuration' or directory listings under /optAffected if The system exposes any CLI command, API endpoint, or script that processes user input without proper sanitization
You are affected if your OS10 version matches any of the vulnerable version ranges and the system permits local user access to input-handling interfaces.
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 · scoped10.5.4.1410.5.5.1310.5.6.8
Apply vendor-supplied patches when available. Until then, limit local access to trusted personnel only, enforce least-privilege principles, and monitor for unusual command execution patterns.
Upgrade to 10.5.4.14 (for 10.5.4.x users), 10.5.5.13 (for 10.5.5.x users), 10.5.6.8 (for 10.5.6.x users), or 10.6.0.2 (for 10.6.0.x users)
- Identify the current SmartFabric OS10 version using 'show version' command
- Determine which version train the current installation belongs to (10.5.4.x, 10.5.5.x, 10.5.6.x, or 10.6.0.x)
- Download the appropriate fixed version from Dell support: for 10.5.4.x train upgrade to 10.5.4.14, for 10.5.5.x upgrade to 10.5.5.13, for 10.5.6.x upgrade to 10.5.6.8, for 10.6.0.x upgrade to 10.6.0.2
- Transfer the upgrade image to the switch using SCP or USB
- Verify the image integrity using 'verify <image> md5' or similar command
- Initiate the upgrade using 'software install <image>' command
- Reboot the device to load the new OS version using 'reload' command
- Confirm the vulnerability is resolved by verifying the new version and running the show version command
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22473 — 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-22473 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