dbcve.org
Data Domain Operating SystemOperating system · Dell

CVE-2024-51534

HIGH · 7.1 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 →
73/100
Remediation priority · Elevated
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 DDOS 8.3.0.0, 7.10.1.50, and 7.13.1.20 contain a path traversal vulnerability. A local low privileged could potentially exploit this vulnerability to gain unauthorized overwrite of OS files stored on the server filesystem. Exploitation could lead to denial of service.

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

Dell PowerProtect DD contains a path traversal vulnerability that allows a local low-privileged user to overwrite OS files on the server filesystem. This occurs due to insufficient input validation in file path handling, potentially enabling arbitrary file write and denial of service.

MitigationUpgrade to DDOS version 8.3.0.0, 7.10.1.50, or 7.13.1.20 or later to remediate. If immediate upgrade is not feasible, limit local access privileges and implement file integrity monitoring.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 installed DDOS version
    Access the Data Domain management interface or CLI and run the command to display the system version (typically 'version' or 'system show version' in DDOS CLI)
    Affected if The version displayed falls within any of these ranges: 7.10.1.0 to 7.10.1.49, 7.13.1.0 to 7.13.1.19, or 7.14.0.0 to 7.2.99.99 (versions below 8.3.0.0)
  2. Confirm system is operational
    Verify the Data Domain system is powered on and running DDOS (the vulnerability is local and requires the OS to be active)
    Affected if The system is running an affected DDOS version as identified in step 1
  3. Verify local user accounts exist
    Check if local user accounts exist on the system by querying the user database (e.g., via 'user list' or similar DDOS CLI command)
    Affected if Local low-privileged accounts are present on a system running an affected version from step 1

You are affected if your Data Domain system is running DDOS version 7.10.1.0-7.10.1.49, 7.13.1.0-7.13.1.19, or 7.14.0.0-7.2.99.99 and has local user accounts that could potentially exploit the path traversal to overwrite OS files.

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

Upgrade to DDOS version 8.3.0.0, 7.10.1.50, or 7.13.1.20 or later to remediate. If immediate upgrade is not feasible, limit local access privileges and implement file integrity monitoring.

Recommended fix High confidence

DDOS 8.3.0.0, 7.10.1.50, or 7.13.1.20 (depending on your current major version branch)

  1. Review the current Data Domain OS version using the 'version' or 'system show version' command
  2. Consult Dell PowerProtect DD upgrade documentation for your current version to ensure compatibility with the target version
  3. Plan maintenance window as upgrade will require system reboot
  4. Backup critical data and configuration according to Dell best practices
  5. Download the appropriate DDOS upgrade image (8.3.0.0, 7.10.1.50, or 7.13.1.20) from Dell Support portal
  6. Upload the upgrade file to the Data Domain system using 'ddboost' or management interface
  7. Initiate upgrade using 'filesys upgrade' command or via management UI
  8. Monitor upgrade progress and verify system comes up successfully post-reboot
Caveat Review Dell upgrade guide for version-specific upgrade paths and ensure proper upgrade sequencing between major releases; some configurations may require migration steps

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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 locally
dbcve dependency scanner

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