CVE-2023-44279
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 PowerProtect DD , versions prior to 7.13.0.10, LTS 7.7.5.25, LTS 7.10.1.15, 6.2.1.110 contain an OS command injection vulnerability in administrator CLI. A local high privileged attacker could potentially exploit this vulnerability, to bypass security restrictions. Exploitation may lead to a system take over by an attacker
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 confidenceOS command injection vulnerability in the administrator CLI of Dell PowerProtect DD. A local high-privileged attacker can inject malicious OS commands through the CLI interface, bypassing security restrictions and potentially achieving complete system compromise.
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< 2.7.6< 6.2.1.110>= 7.0, < 7.10.1.15< 6.2.1.110>= 7.0, < 7.12.0.0< 6.2.1.110>= 7.0, < 7.13.0.10>= 7.7, < 7.7.5.25>= 7.10, < 7.10.1.15< 6.2.1.110>= 7.0, < 7.12.0.0>= 7.7, < 7.7.5.25>= 7.10, < 7.10.1.15CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 the Dell product nameCheck the system documentation, login banner, or run 'system show product' in the CLI to confirm whether the system is Dell PowerProtect Data Protection, Dell Apex Protection Storage, Dell PowerProtect Data Domain, Dell PowerProtect Data Domain Management Center, or Dell EMC Data Domain OS.Affected if The product is any of these five affected products.
-
Retrieve the installed software versionAccess the administrative CLI and run the version command appropriate to the product, such as 'version', 'system show version', or 'software show version' to obtain the exact installed release number.Affected if The version cannot be determined or is returned as 'unknown'.
-
Compare version to affected ranges for PowerProtect Data ProtectionIf the product is Dell PowerProtect Data Protection, check if the version is lower than 2.7.6.Affected if Installed version < 2.7.6.
-
Compare version to affected ranges for Apex Protection StorageIf the product is Dell Apex Protection Storage, check if version is < 6.2.1.110 OR (>= 7.0 and < 7.10.1.15).Affected if Installed version < 6.2.1.110 OR (>= 7.0 and < 7.10.1.15).
-
Compare version to affected ranges for PowerProtect Data DomainIf the product is Dell PowerProtect Data Domain, check if version is < 6.2.1.110 OR (>= 7.0 and < 7.12.0.0).Affected if Installed version < 6.2.1.110 OR (>= 7.0 and < 7.12.0.0).
-
Compare version to affected ranges for Data Domain Management CenterIf the product is Dell PowerProtect Data Domain Management Center, check if version is < 6.2.1.110 OR (>= 7.0 and < 7.13.0.10) OR (>= 7.7 and < 7.7.5.25) OR (>= 7.10 and < 7.10.1.15).Affected if Installed version matches any of these vulnerable ranges.
If the product is any of the five affected Dell products and the installed version falls within any of the specified vulnerable ranges, the environment is affected by CVE-2023-44279.
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 · scoped2.7.66.2.1.1107.7.5.25
Apply vendor-provided patches to reach fixed versions: 7.13.0.10, LTS 7.7.5.25, LTS 7.10.1.15, or 6.2.1.110 or later. Restrict CLI access to only necessary trusted administrators.
Upgrade to Dell PowerProtect DD 7.13.0.10 (or later), LTS 7.7.5.25, LTS 7.10.1.15, or 6.2.1.110 depending on product and release train
- Identify the specific Dell PowerProtect product and current version from the affected versions list
- Determine the appropriate upgrade path based on the current version (LTS or current release train)
- For Powerprotect Data Domain Management Center: upgrade to version 7.13.0.10 or later, or to LTS 7.7.5.25 or 7.10.1.15
- For Powerprotect Data Domain: upgrade to version 7.12.0.0 or later, or to LTS 6.2.1.110 or 7.10.1.15
- For Apex Protection Storage: upgrade to version 7.10.1.15 or later, or to LTS 6.2.1.110
- For Powerprotect Data Protection: upgrade to version 2.7.6 or later
- For Emc Data Domain Os: upgrade to version 7.12.0.0 or later, or to LTS 7.7.5.25 or 7.10.1.15 or 6.2.1.110
- Download the upgrade from Dell support portal (www.dell.com/support)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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 $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44279 — 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-44279 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