CVE-2023-48667
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 remote high privileged attacker could potentially exploit this vulnerability, leading to the execution of arbitrary OS commands on the application's underlying OS to bypass security restriction. 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 allows a remote high-privileged attacker to execute arbitrary OS commands on the underlying operating system, bypassing security restrictions and potentially achieving full 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< 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.15< 2.7.6CVSS 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 installed product and versionAccess the system CLI or administrative interface and run the command to display the system version (for example: 'system show version' or check the About/System Info page in the management console). Note the exact version number.Affected if The version matches any of the affected ranges: < 6.2.1.110; >= 7.0, < 7.10.1.15; >= 7.0, < 7.12.0.0; >= 7.0, < 7.13.0.10; >= 7.7, < 7.7.5.25; >= 7.10, < 7.10.1.15; or for Powerprotect Data Protection < 2.7.6.
-
Determine the product typeConfirm which Dell product is running: Dell Apex Protection Storage, Dell PowerProtect Data Domain, Dell PowerProtect Data Domain Management Center, Dell EMC Data Domain OS, or Dell PowerProtect Data Protection. Each has different affected version ranges.Affected if The product is any of these five and the version falls within the corresponding affected ranges.
-
Verify administrator CLI accessibilityCheck network configuration to determine if the administrative CLI (typically accessible via SSH on port 22 or the web-based management interface) is exposed to network segments beyond the trusted management network.Affected if The administrator CLI is accessible from untrusted network segments or the internet, allowing remote high-privileged attackers to reach it.
-
Check for high-privileged user accountsReview user account configurations in the administrative interface to identify accounts with high-privileged access (administrator-level privileges) that could be leveraged for command injection.Affected if High-privileged administrative accounts exist in the system, which is required for exploitation.
The environment is affected if the installed Dell PowerProtect DD product version falls within any of the specified vulnerable version ranges AND the administrator CLI is network-accessible to potential attackers.
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 command injection vulnerability.
Upgrade to version 7.13.0.10 (or latest stable) for PowerProtect DD; 7.7.5.25 for LTS 7.7 branch; 7.10.1.15 for LTS 7.10 branch; or 6.2.1.110 for older branches; PowerProtect Data Protection to 2.7.6 or later
- 1. Identify the exact Dell PowerProtect product and current version running in your environment from the following: Apex Protection Storage, Powerprotect Data Domain, Powerprotect Data Domain Management Center, Emc Data Domain Os, or Powerprotect Data Protection
- 2. Consult Dell support documentation at www.dell.com to obtain the specific upgrade package for your product
- 3. Schedule a maintenance window as upgrades may require system downtime
- 4. Backup all critical data and configuration settings before proceeding
- 5. Follow Dell's documented upgrade procedure for your specific product version
- 6. Verify the upgrade was successful and the system is operational
- 7. Confirm the new version matches or exceeds the fixed release: 7.13.0.10, 7.7.5.25, 7.10.1.15, or 6.2.1.110 depending on your product line
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48667 — 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-48667 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