dbcve.org
Data Domain Operating SystemOperating system · Dell

CVE-2024-37139

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 contain an Improper Control of a Resource Through its Lifetime vulnerability in an admin operation. A remote low privileged attacker could potentially exploit this vulnerability, leading to temporary resource constraint of system application. Exploitation may lead to denial of service of the application.

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 an improper control of resource through its lifetime vulnerability in an admin operation. A remote low privileged attacker can exploit this to cause temporary resource constraints on the system application, potentially leading to denial of service. The vulnerability affects versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, and LTS 7.7.5.40.

MitigationApply vendor-supplied patches by upgrading to Dell PowerProtect DD version 8.0 or later, or the specified LTS versions (7.13.1.0, 7.10.1.30, 7.7.5.40) or later. Coordinate a maintenance window for the upgrade and validate functionality post-patch.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
    Access the Data Domain CLI or management interface and retrieve the installed OS version. Common methods include running 'show version' via SSH or checking the system information in the management GUI.
    Affected if The version displayed is less than 7.7.5.40, or falls within 7.8.0.0 to 7.10.1.29, or falls within 7.11.0.0 to 7.13.0.9.
  2. Confirm the exact version number
    Record the full version string including any build numbers or patch levels (for example, 7.10.1.0-123456). Compare this against the documented vulnerable ranges.
    Affected if The version is any build prior to the fixed LTS releases (7.7.5.40, 7.10.1.30, 7.13.1.0) or prior to 8.0.
  3. Verify the product model
    Confirm the system is a Dell PowerProtect DD or Dell Data Domain appliance. This vulnerability affects the Data Domain Operating System specifically.
    Affected if The installed product is a Dell PowerProtect DD or Data Domain system running a vulnerable OS version from step 1.

If the Data Domain OS version is below 7.7.5.40, between 7.8.0.0 and 7.10.1.29, or between 7.11.0.0 and 7.13.0.9, the system is affected by this vulnerability.

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

Apply vendor-supplied patches by upgrading to Dell PowerProtect DD version 8.0 or later, or the specified LTS versions (7.13.1.0, 7.10.1.30, 7.7.5.40) or later. Coordinate a maintenance window for the upgrade and validate functionality post-patch.

Recommended fix Moderate confidence

Upgrade to LTS 7.7.5.40, LTS 7.10.1.30, LTS 7.13.1.0, or version 8.0 or later (whichever is the next sequential release in your current branch)

  1. 1. Identify the current Data Domain Operating System version using the 'version' or 'system show version' command.
  2. 2. Determine the appropriate upgrade path based on the current version - upgrades must follow Dell's documented upgrade path (typically sequential minor version upgrades).
  3. 3. Download the Dell PowerProtect DD firmware from Dell Support (support.dell.com) - obtain the fixed version that corresponds to your current branch: 7.7.5.40 or later for 7.7.x, 7.10.1.30 or later for 7.8.x/7.9.x/7.10.x, 7.13.1.0 or later for 7.11.x/7.12.x/7.13.x, or 8.0 or later.
  4. 4. Review the Data Domain upgrade guide for pre-upgrade requirements including backup, health checks, and downtime window.
  5. 5. Upload the firmware file using 'file upload' or via the Data Domain Enterprise Manager.
  6. 6. Initiate the upgrade using 'system upgrade' command or through the management UI.
  7. 7. Verify the upgrade completed successfully and the system is operational.
  8. 8. Confirm the new version is no longer in the affected range by running 'version' command.
Caveat Follow sequential upgrade path as documented in Dell upgrade guide; ensure compatibility with any integrated backup software; schedule maintenance window as upgrade may cause application downtime

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
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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