CVE-2023-43072
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 Storage Software v1.4 (and earlier) contains an improper access control vulnerability in the CLI. A local possibly unauthenticated attacker could potentially exploit this vulnerability, leading to ability to execute arbritrary shell commands.
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 Storage Software v1.4 and earlier contains an improper access control vulnerability in its CLI that allows a local, possibly unauthenticated attacker to execute arbitrary shell commands. This is a high-severity local privilege escalation vulnerability in the command-line 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< 1.4.1CVSS 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 installed Dell SmartFabric Storage Software versionRun the software's version command or check the product's about/info section. Common methods include running 'dellsfs --version' or accessing the management interface to view version information.Affected if The installed version is 1.4 or earlier (any version < 1.4.1).
-
Assess local access to the systemDetermine if the system can be accessed locally by untrusted users. Check physical access controls and console login availability.Affected if Untrusted local users or unauthenticated attackers can gain local access to the system hosting the CLI.
A system is affected if it runs Dell SmartFabric Storage Software version 1.4 or earlier AND has the CLI component accessible to local users.
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 · scoped1.4.1
Upgrade to a patched version of Dell SmartFabric Storage Software beyond v1.4. If patching is immediately unavailable, restrict physical and logical access to systems hosting the CLI and monitor for unauthorized access attempts.
1.4.1 or later
- Verify current Dell SmartFabric Storage Software version using the CLI or web interface
- Download SmartFabric Storage Software version 1.4.1 or later from Dell Support (support.dell.com)
- Review Dell upgrade documentation for SmartFabric Storage Software
- Schedule upgrade during a maintenance window as the CLI component may require system update
- Back up current configuration before initiating upgrade
- Upload the upgrade package and execute the upgrade via CLI or management interface
- Verify successful upgrade to version 1.4.1 or later
- Confirm the improper access control vulnerability is remediated by verifying CLI access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.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,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43072 — 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-2023-43072 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