CVE-2023-44285
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 improper access control vulnerability. A local malicious user with low privileges could potentially exploit this vulnerability leading to escalation of privilege.
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 confidenceDell PowerProtect DD contains an improper access control vulnerability that allows a local user with low privileges to escalate their privileges to a higher level. The vulnerability exists due to insufficient access control checks in the affected versions, enabling a malicious local user to gain unauthorized elevated access.
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 productRun 'system show product' or check /etc/product_name on the Dell PowerProtect/Data Domain system to confirm which product is running (Data Protection, Apex Protection Storage, Data Domain, Data Domain Management Center, or EMC Data Domain OS)Affected if The product matches any of the five affected product families listed in the CVE
-
Retrieve the installed software versionExecute the version command specific to your product: 'version' or 'ddr version' for Data Domain systems, or check the system information GUI/CLI for PowerProtect appliancesAffected if Unable to determine the version number from the system
-
Compare version against affected ranges for Dell PowerProtect Data ProtectionIf running Data Protection, compare your version to: < 2.7.6Affected if Your installed version is below 2.7.6
-
Compare version against affected ranges for Dell Apex Protection StorageIf running Apex Protection Storage, compare your version to: < 6.2.1.110 OR >= 7.0 but < 7.10.1.15Affected if Your installed version is below 6.2.1.110, or between 7.0 and 7.10.1.15 (excluding 7.10.1.15)
-
Compare version against affected ranges for Dell PowerProtect Data DomainIf running Data Domain, compare your version to: < 6.2.1.110 OR >= 7.0 but < 7.12.0.0Affected if Your installed version is below 6.2.1.110, or between 7.0 and 7.12.0.0 (excluding 7.12.0.0)
-
Compare version against affected ranges for Dell Data Domain Management Center and EMC Data Domain OSFor Management Center: check < 6.2.1.110 OR >= 7.0 but < 7.13.0.10 OR >= 7.7 but < 7.7.5.25 OR >= 7.10 but < 7.10.1.15. For EMC Data Domain OS: check < 6.2.1.110 OR >= 7.0 but < 7.12.0.0 OR >= 7.7 but < 7.7.5.25 OR >= 7.10 but < 7.10.1.15Affected if Your installed version falls into any of the vulnerable version ranges for your product
You are affected if your Dell PowerProtect or Data Domain product version is within any of the vulnerable ranges listed for your specific product, since this local privilege escalation requires the system to be running a vulnerable version with the default access control configuration.
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 6.2.1.110 or later to remediate this vulnerability.
Upgrade to version 6.2.1.110 (for 6.x), 7.7.5.25 (for 7.0-7.6.x), 7.10.1.15 (for 7.7-7.9.x), or 7.13.0.10 (for 7.10+) depending on current branch
- 1. Identify the specific product (PowerProtect DD, Apex Protection Storage, Data Domain Management Center, EMC Data Domain OS, or PowerProtect Data Protection) and current installed version using the system management interface or CLI.
- 2. Based on the current version branch, determine the appropriate target fixed release: for 6.x branch upgrade to 6.2.1.110; for 7.0-7.6.x upgrade to 7.7.5.25; for 7.7-7.9.x upgrade to 7.10.1.15; for 7.10-7.12.x upgrade to 7.13.0.10.
- 3. Review the product's upgrade guide and release notes for prerequisites, pre-upgrade checks, and any migration considerations.
- 4. Create a backup of current configuration and verify data integrity before initiating upgrade.
- 5. Schedule maintenance window as upgrade may require system restart.
- 6. Download the appropriate upgrade package from Dell support portal (support.dell.com).
- 7. Execute the upgrade following the documented procedure for the specific product (ddupgrade for Data Domain, management center console for DDMC, etc.).
- 8. After upgrade completes, verify system status and confirm version number matches target fixed release.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44285 — 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-44285 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