CVE-2023-44278
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 a path traversal vulnerability. A local high privileged attacker could potentially exploit this vulnerability, to gain unauthorized read and write access to the OS files stored on the server filesystem, with the privileges of the running application.
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 a path traversal vulnerability that allows a local high-privileged attacker to manipulate file path inputs to gain unauthorized read and write access to arbitrary OS files on the server filesystem, executing with the privileges of the application process.
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 installed product and versionRun command to determine Dell PowerProtect product installed (e.g., 'ddr version', 'systemshow', or check appliance management console for product version)Affected if Version is Dell PowerProtect DD, Data Domain, or related product and is below 2.7.6, 6.2.1.110, 7.10.1.15, 7.12.0.0, 7.13.0.10, or 7.7.5.25 depending on product line
-
Confirm product type matches affected linesVerify product is one of: Dell Powerprotect Data Protection, Dell Apex Protection Storage, Dell Powerprotect Data Domain, Dell Powerprotect Data Domain Management Center, or Dell EMC Data Domain OSAffected if Product is any of the listed affected product lines and version falls within affected ranges
-
Verify the system has local user accessConfirm local authenticated access is possible (path traversal requires local high-privileged attacker on the system)Affected if Local high-privileged user accounts exist on the system, enabling exploitation of this vulnerability
User is affected if running any Dell PowerProtect DD, Data Domain, or related product version below the patched releases (6.2.1.110, 7.10.1.15, 7.12.0.0, 7.13.0.10, 7.7.5.25, or 2.7.6 depending on product line) and local privileged access exists on the appliance.
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, 6.2.1.110 or later to obtain the patch that addresses this vulnerability.
Upgrade to version 6.2.1.110, 7.7.5.25 (LTS), 7.10.1.15 (LTS), or 7.13.0.10 depending on the product and release track
- Identify the currently installed version of the affected Dell PowerProtect product
- Download the appropriate fixed version from Dell support: 6.2.1.110, 7.7.5.25 (LTS), 7.10.1.15 (LTS), or 7.13.0.10
- Review Dell upgrade documentation and release notes for the target version
- Perform a complete backup of the system and verify data integrity
- Schedule a maintenance window to minimize business impact
- Execute the upgrade following Dell's documented upgrade procedure for the specific product
- Verify the upgrade was successful by checking the new version number
- Confirm the path traversal vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44278 — 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-44278 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