CVE-2023-44277
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 the CLI. A local low privileged attacker could potentially exploit this vulnerability, leading to the execution of arbitrary OS commands on the application's underlying OS, with the privileges of the vulnerable application. 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 CLI of Dell PowerProtect DD allows a local low-privileged attacker to execute arbitrary OS commands with application-level privileges, 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
- 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.
-
Identify the installed Dell product and versionAccess the system CLI or management interface and run the version command (such as 'version', 'system show version', or 'ddr version' depending on the product). Alternatively, check the management console for the installed version information.Affected if The installed version falls within any of these ranges: PowerProtect Data Protection < 2.7.6; Apex Protection Storage < 6.2.1.110 or >= 7.0 and < 7.10.1.15; PowerProtect Data Domain < 6.2.1.110 or >= 7.0 and < 7.12.0.0; PowerProtect Data Domain Management Center < 6.2.1.110 or >= 7.0 and < 7.13.0.10
-
Verify CLI interface is accessibleConfirm that the command-line interface is enabled and accessible on the system. This may involve testing SSH access or local console access to the Dell CLI environment.Affected if CLI access is available to any user on the system
-
Confirm low-privileged user CLI access existsCheck if non-administrative or low-privilege accounts can access the CLI and execute commands. Review user role assignments and CLI permission settings if available.Affected if Low-privileged users can access and interact with the CLI interface
You are affected if your installed Dell PowerProtect DD product version is below the fixed releases AND the CLI interface is 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 · scoped2.7.66.2.1.1107.7.5.25
Upgrade Dell PowerProtect DD to version 7.13.0.10, LTS 7.7.5.25, LTS 7.10.1.15, or later to remediate the vulnerability.
Upgrade to version 6.2.1.110, LTS 7.7.5.25, LTS 7.10.1.15, 7.12.0.0, or 7.13.0.10 depending on your product and release line (LTS or current)
- 1. Identify the specific Dell PowerProtect product and current version in your environment from the affected products list (PowerProtect Data Protection, Apex Protection Storage, PowerProtect Data Domain, PowerProtect Data Domain Management Center, or EMC Data Domain OS)
- 2. Consult Dell's official support portal at www.dell.com to obtain the appropriate patched version for your specific product
- 3. Schedule a maintenance window for the upgrade procedure
- 4. Back up all critical data and configurations according to your organization's backup policy
- 5. Follow Dell's documented upgrade procedure for your specific product to apply the fixed version (6.2.1.110, 7.7.5.25, 7.10.1.15, 7.12.0.0, or 7.13.0.10 depending on product and release line)
- 6. After upgrade, verify the new version is running and confirm the vulnerability is remediated
- 7. Validate that all expected functionality and protected workloads are operational post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44277 — 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-44277 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