dbcve.org
Data Domain Operating SystemOperating system · Dell

CVE-2024-29175

MEDIUM · 5.9 CVSS v3.1 Published 2024-06-26
Fix available
A fix is available. Upgrade to 7.7.5.40 / 7.10.1.30 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 7.13.0.0, LTS 7.7.5.40, LTS 7.10.1.30 contain an weak cryptographic algorithm vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability, leading to man-in-the-middle attack that exposes sensitive session information.

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 Data Domain versions prior to 7.13.0.0 and specified LTS versions contain weak cryptographic algorithms that enable a remote unauthenticated attacker to perform man-in-the-middle attacks, potentially exposing sensitive session information.

MitigationUpgrade Dell PowerProtect Data Domain to version 7.13.0.0 or later, or apply the LTS patches (7.7.5.40 or 7.10.1.30) to remediate the weak cryptographic algorithm 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.7.5.40>= 7.8.0.0, < 7.10.1.30>= 7.11.0.0, < 7.13.1.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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 Data Domain OS version
    Log into the Data Domain CLI and run the command to display the system version. Typically, this is done using the `version` command or by checking `/etc/dd_version` or similar system information files accessible via admin shell.
    Affected if The installed version falls into any of these ranges: < 7.7.5.40, >= 7.8.0.0 and < 7.10.1.30, or >= 7.11.0.0 and < 7.13.1.0.
  2. Confirm the exact version number
    Use the Data Domain management interface or CLI to retrieve the full version string including the build number. Compare this against the specific patch versions mentioned (7.7.5.40, 7.10.1.30, 7.13.1.0).
    Affected if The exact version is lower than 7.7.5.40, or is between 7.8.0.0 and 7.10.1.30 (exclusive), or between 7.11.0.0 and 7.13.1.0 (exclusive).
  3. Determine if remote management interfaces are exposed
    Check network configuration to see if Data Domain management interfaces (such as the web UI, SSH, or API endpoints) are accessible from untrusted networks or the internet. Review firewall rules and access lists.
    Affected if The management or administrative interfaces are reachable from outside the trusted network, making the weak cryptographic algorithms exploitable by remote attackers.

A user is affected if their Data Domain OS version is below 7.7.5.40, between 7.8.0.0 and 7.10.1.30, or between 7.11.0.0 and 7.13.1.0, and the management interface is network-accessible to untrusted parties.

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.40 / 7.10.1.30 / 7.13.1.0 or later
Fixed in 7.7.5.407.10.1.307.13.1.0
Interim mitigation

Upgrade Dell PowerProtect Data Domain to version 7.13.0.0 or later, or apply the LTS patches (7.7.5.40 or 7.10.1.30) to remediate the weak cryptographic algorithm vulnerability.

Recommended fix High confidence

7.7.5.40 (for 7.7.x branch), 7.10.1.30 (for 7.8-7.10 branch), or 7.13.1.0 (for 7.11+ branch) - choose the appropriate LTS release based on current branch

  1. 1. Identify the currently installed Data Domain Operating System version via the management console or CLI: 'system show version'
  2. 2. Determine which version branch your current installation belongs to (7.7.x, 7.8.x-7.10.x, or 7.11.x-7.13.x)
  3. 3. For systems on 7.7.x branch: Upgrade to version 7.7.5.40 or later
  4. 4. For systems on 7.8.x-7.10.x branch: Upgrade to version 7.10.1.30 or later
  5. 5. For systems on 7.11.x-7.13.x branch: Upgrade to version 7.13.1.0 or later
  6. 6. After upgrade, verify the new version is running: 'system show version'
  7. 7. Test that critical data protection operations function normally post-upgrade
Caveat Standard LTS upgrade precautions apply; review Dell upgrade documentation for specific migration steps and ensure valid backup exists 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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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