Data Domain Operating SystemOperating system · Dell

CVE-2024-45759

HIGH · 7.3 CVSS v3.1 Published 2024-11-08
Fix available
A fix is available. Upgrade to 7.7.5.50 / 7.10.1.40 or later.
See remediation →
75/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 Data Domain, versions prior to 8.1.0.0, 7.13.1.10, 7.10.1.40, and 7.7.5.50, contains an escalation of privilege vulnerability. A local low privileged attacker could potentially exploit this vulnerability, leading to unauthorized execution of certain commands to overwrite system config of the application. Exploitation may lead to denial of service of system.

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 Data Domain versions prior to 8.1.0.0, 7.13.1.10, 7.10.1.40, and 7.7.5.50 contain a local privilege escalation vulnerability allowing a low-privileged authenticated attacker to overwrite system configuration files, potentially causing denial of service.

MitigationUpgrade to Dell PowerProtect Data Domain versions 8.1.0.0, 7.13.1.10, 7.10.1.40, or 7.7.5.50 or later per Dell's security advisory.

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.7.1.0, < 7.7.5.50>= 7.10.0.0, < 7.10.1.40>= 7.13.0.0, < 7.13.1.10>= 8.0.0.0, < 8.1.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
Low
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/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. Determine installed Data Domain OS version
    Run the command 'version' or 'show version' on the Data Domain CLI to retrieve the system software version
    Affected if The version displayed falls within any of these ranges: 7.7.1.0 to 7.7.5.49, 7.10.0.0 to 7.10.1.39, 7.13.0.0 to 7.13.1.9, or 8.0.0.0 to 8.0.9.9 (or any 8.0.x.x version below 8.1.0.0)
  2. Confirm product is PowerProtect Data Domain
    Verify the system is a Dell PowerProtect Data Domain appliance by checking the product model via 'hardware info' or 'system show model' command output
    Affected if The system is a Dell PowerProtect Data Domain model running a vulnerable OS version from step 1
  3. Identify authentication configuration
    Check if local user accounts exist with low-privileged access by reviewing 'user list' or 'show users' command output in the Data Domain CLI
    Affected if Low-privileged authenticated users are present on the system (this is the prerequisite for the privilege escalation to be exploitable)
  4. Review file permissions on system configuration
    Inspect the permissions of critical configuration files in /etc or /data/colony/etc using 'ls -la' if accessible, or review audit logs for any unauthorized modifications
    Affected if Configuration files show unexpected modification timestamps or permission changes indicating the vulnerability may have been exploited

A system is affected if it runs Dell Data Domain Operating System version 7.7.1.0 through 7.7.5.49, 7.10.0.0 through 7.10.1.39, 7.13.0.0 through 7.13.1.9, or any 8.0.x.x version below 8.1.0.0 and has low-privileged user accounts configured.

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.7.5.50 / 7.10.1.40 / 7.13.1.10 or later
Fixed in 7.7.5.507.10.1.407.13.1.10
Interim mitigation

Upgrade to Dell PowerProtect Data Domain versions 8.1.0.0, 7.13.1.10, 7.10.1.40, or 7.7.5.50 or later per Dell's security advisory.

Recommended fix High confidence

Upgrade to 7.7.5.50 (for 7.7.x), 7.10.1.40 (for 7.10.x), 7.13.1.10 (for 7.13.x), or 8.1.0.0 (for 8.0.x) depending on your current branch

  1. 1. Back up the current Data Domain system configuration and verify the backup is restorable
  2. 2. Download the appropriate fixed version from Dell Support portal (www.dell.com/support)
  3. 3. Schedule a maintenance window as the upgrade may require system downtime
  4. 4. For 7.7.x branch: upgrade to version 7.7.5.50 or later
  5. 5. For 7.10.x branch: upgrade to version 7.10.1.40 or later
  6. 6. For 7.13.x branch: upgrade to version 7.13.1.10 or later
  7. 7. For 8.0.x branch: upgrade to version 8.1.0.0
  8. 8. Follow Dell's official upgrade procedure for PowerProtect Data Domain
Caveat Standard maintenance upgrade; review Dell release notes for any specific compatibility notes

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

Fix this in Data Domain Operating System Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45759 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