dbcve.org
Powerprotect Data ProtectionApplication · Dell

CVE-2023-44286

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 2.7.6 / 6.2.1.110 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Dell 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 DOM-based Cross-Site Scripting vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability, leading to the injection of malicious HTML or JavaScript code to a victim user's DOM environment in the browser. . Exploitation may lead to information disclosure, session theft, or client-side request forgery.

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 confidence

DOM-based Cross-Site Scripting vulnerability in Dell PowerProtect DD allows unauthenticated remote attackers to inject malicious HTML or JavaScript code into a victim's DOM environment via vulnerable client-side script handling. Successful exploitation can lead to information disclosure, session theft, or client-side request forgery.

MitigationUpgrade to Dell PowerProtect DD versions 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.

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
Powerprotect Data ProtectionApplication
Affected:< 2.7.6
Apex Protection StorageApplication
Affected:< 6.2.1.110>= 7.0, < 7.10.1.15
Powerprotect Data DomainApplication
Affected:< 6.2.1.110>= 7.0, < 7.12.0.0
Powerprotect Data Domain Management CenterApplication
Affected:< 6.2.1.110>= 7.0, < 7.13.0.10>= 7.7, < 7.7.5.25>= 7.10, < 7.10.1.15
Emc Data Domain OsOperating system
Affected:< 6.2.1.110>= 7.0, < 7.12.0.0>= 7.7, < 7.7.5.25>= 7.10, < 7.10.1.15

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Dell product
    Log into the system CLI or management interface and run 'version' or 'system show version' to identify the exact product name (PowerProtect DD, Data Domain, Apex Protection Storage, etc.)
    Affected if The 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 OS
  2. Obtain the installed software version
    Run the version command specific to the product (e.g., 'ddos -version' for Data Domain, or check the management console UI for version information)
    Affected if Unable to retrieve a version number prevents further vulnerability assessment
  3. Compare against affected version ranges for PowerProtect Data Protection
    If running PowerProtect Data Protection, compare your version to: < 2.7.6
    Affected if Version is less than 2.7.6 - you are affected
  4. Compare against affected version ranges for PowerProtect Data Domain
    If running PowerProtect Data Domain, compare your version to: < 6.2.1.110 OR >= 7.0 AND < 7.12.0.0
    Affected if Version falls into any of these ranges: < 6.2.1.110, >= 7.0 but < 7.12.0.0 - you are affected
  5. Compare against affected version ranges for Data Domain Management Center
    If running Data Domain Management Center, compare to: < 6.2.1.110, >= 7.0 but < 7.13.0.10, >= 7.7 but < 7.7.5.25, >= 7.10 but < 7.10.1.15
    Affected if Version falls into any of these ranges: < 6.2.1.110, >= 7.0 but < 7.13.0.10, >= 7.7 but < 7.7.5.25, or >= 7.10 but < 7.10.1.15 - you are affected
  6. Compare against affected version ranges for EMC Data Domain OS
    If running Dell EMC Data Domain OS, compare to: < 6.2.1.110, >= 7.0 but < 7.12.0.0, >= 7.7 but < 7.7.5.25, >= 7.10 but < 7.10.1.15
    Affected if Version falls into any of these ranges: < 6.2.1.110, >= 7.0 but < 7.12.0.0, >= 7.7 but < 7.7.5.25, or >= 7.10 but < 7.10.1.15 - you are affected

You are affected if your installed Dell product version falls within any of the specified vulnerable ranges for your specific product, and the web management interface is accessible to potentially trigger the DOM-based XSS.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.7.6 / 6.2.1.110 / 7.7.5.25 or later
Fixed in 2.7.66.2.1.1107.7.5.25
Interim mitigation

Upgrade to Dell PowerProtect DD versions 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.

Recommended fix High confidence

6.2.1.110 (6.x) | 7.7.5.25 (LTS 7.7) | 7.10.1.15 (LTS 7.10) | 7.13.0.10 (7.x mainline)

  1. 1. Identify the currently installed PowerProtect Data Domain / DDmc / EMC Data Domain OS version from the system management interface
  2. 2. Determine which release branch is in use (legacy 6.x, LTS 7.7.x, LTS 7.10.x, or 7.x mainline)
  3. 3. For systems on 6.x branch: upgrade to version 6.2.1.110 or later
  4. 4. For systems on LTS 7.7.x branch: upgrade to version 7.7.5.25 or later
  5. 5. For systems on LTS 7.10.x branch: upgrade to version 7.10.1.15 or later
  6. 6. For systems on 7.x mainline (7.0+): upgrade to version 7.13.0.10 or later
  7. 7. After upgrade, verify the XSS vulnerability is resolved by reviewing release notes and confirming system functionality
Caveat Upgrades may require downtime; review Dell upgrade documentation for prerequisites and compatibility with existing backup infrastructure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powerprotect Data Protection Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-44286 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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