dbcve.org
Data Domain Operating SystemOperating system · Dell

CVE-2024-53295

HIGH · 7.8 CVSS v3.1 Published 2025-02-01
Fix available
A fix is available. Upgrade to 7.10.1.50 / 7.13.1.20 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 8.3.0.0, 7.10.1.50, and 7.13.1.20 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 · moderate confidence

Dell PowerProtect DD backup appliance contains an improper access control vulnerability that allows a low-privilege local user to escalate privileges to higher levels. The vulnerability exists in versions prior to 8.3.0.0, 7.10.1.50, and 7.13.1.20, and is exploited through local access rather than remote attacks.

MitigationApply the vendor-supplied software updates (version 8.3.0.0, 7.10.1.50, 7.13.1.20 or later) to all affected Dell PowerProtect DD systems to remediate the improper access control 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
Data Domain Operating SystemOperating system
Affected:>= 7.10.1.0, < 7.10.1.50>= 7.13.1.0, < 7.13.1.20>= 7.14.0.0, < 8.3.0.0

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
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 checks

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

  1. Identify the Data Domain OS version
    Use the system CLI command to display the installed version (for example, `version` or `system show version` from the DDOS shell). Record the full version number including build information.
    Affected if The installed version falls within any of these ranges: >= 7.10.1.0 and < 7.10.1.50; >= 7.13.1.0 and < 7.13.1.20; >= 7.14.0.0 and < 8.3.0.0
  2. Verify the exact version string
    Confirm the complete version number reported by the system. Compare the major.minor.patch.build format against the fixed versions 8.3.0.0, 7.10.1.50, and 7.13.1.20.
    Affected if The version is earlier than 8.3.0.0, 7.10.1.50, or 7.13.1.20 (the specific threshold depends on the 7.10.x or 7.13.x or 7.14.x branch in use).
  3. Confirm local user access exists
    Check if low-privilege local user accounts are configured on the system. Use system management commands to list local users (for example, `user list` or equivalent from the DDOS administrative interface).
    Affected if Local user accounts with limited privileges exist on the system and the DDOS version is in a vulnerable range.

The system is affected if the installed Dell Data Domain Operating System version is lower than 8.3.0.0, 7.10.1.50, or 7.13.1.20 (depending on the release branch) AND local user accounts are present.

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 7.10.1.50 / 7.13.1.20 / 8.3.0.0 or later
Fixed in 7.10.1.507.13.1.208.3.0.0
Interim mitigation

Apply the vendor-supplied software updates (version 8.3.0.0, 7.10.1.50, 7.13.1.20 or later) to all affected Dell PowerProtect DD systems to remediate the improper access control vulnerability.

Recommended fix High confidence

Upgrade to 7.10.1.50 (for 7.10.x), 7.13.1.20 (for 7.13.x), or 8.3.0.0 (for 7.14.x)

  1. Identify the current Data Domain Operating System version using the system CLI or management interface
  2. Determine the appropriate upgrade path based on current version: if 7.10.x branch, upgrade to 7.10.1.50; if 7.13.x branch, upgrade to 7.13.1.20; if 7.14.x branch, upgrade to 8.3.0.0
  3. Review Dell PowerProtect DD upgrade documentation and release notes for the target version
  4. Create a backup of critical data and configuration settings
  5. Schedule maintenance window as upgrades require system downtime
  6. Follow Dell's standard upgrade procedure (typically via the system CLI or management interface)
  7. After upgrade completes, verify the new version is at or above the fixed release (7.10.1.50, 7.13.1.20, or 8.3.0.0)
  8. Confirm the vulnerability is resolved
Caveat Standard upgrade risks apply - review release notes for any compatibility or configuration changes before proceeding

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

Fix this in Data Domain Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53295 — 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-2024-53295 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