CVE-2024-37138
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 · uneditedDell PowerProtect DD, versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, LTS 7.7.5.40 on DDMC contain a relative path traversal vulnerability. A remote high privileged attacker could potentially exploit this vulnerability, leading to the application sending over an unauthorized file to the managed 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 confidenceDell PowerProtect DD versions prior to 8.0, LTS 7.13.1.0, LTS 7.10.1.30, and LTS 7.7.5.40 on DDMC contain a relative path traversal vulnerability that allows a remote high-privileged attacker to force the application to send unauthorized files from the managed system to an attacker-controlled location.
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< 7.7.5.40>= 7.8.0.0, < 7.10.1.30>= 7.11.0.0, < 7.13.1.0CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify DDMC version via CLILog into the Data Domain system via SSH and run the command 'ddmc -version' or 'system show version' to retrieve the DDMC version informationAffected if The displayed version falls within the affected ranges: < 7.7.5.40, >= 7.8.0.0 and < 7.10.1.30, >= 7.11.0.0 and < 7.13.1.0, or < 8.0 (if newer branch)
-
Confirm DDMC is enabledRun the command 'ddmc status' or check if the DDMC service is active using 'system services show' to determine if Data Domain Management Center is currently enabled on the systemAffected if DDMC is enabled and the version is in the affected ranges from step 1
-
Determine if system is DDMC or managed systemExecute 'ddmc show' or 'ddmc -c' to identify whether this system is the DDMC central management console or a managed system. The vulnerability affects the DDMC component specificallyAffected if This system is the DDMC (central management) and the version is affected, meaning it can be coerced to send files from managed systems
-
Check DDMC file transfer configurationReview DDMC file transfer or export configuration using 'ddmc export-path show' or similar commands to see if file transfer paths are configuredAffected if File transfer/export paths are configured on an affected DDMC version, which could be exploited for path traversal
-
Compare installed version against fixed releasesVerify the exact version number obtained in step 1 against the fixed releases: 8.0 or later, LTS 7.13.1.0 or later, LTS 7.10.1.30 or later, LTS 7.7.5.40 or laterAffected if The installed version is lower than any of these fixed releases
A system is affected if it runs DDMC (Data Domain Management Center) with a version in the vulnerable ranges and the DDMC service is enabled, allowing a remote high-privileged attacker to exploit the relative path traversal to exfiltrate files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.7.5.407.10.1.307.13.1.0
Apply vendor-provided patches for affected versions or upgrade to the fixed releases (8.0 or later, LTS 7.13.1.0 or later, LTS 7.10.1.30 or later, LTS 7.7.5.40 or later). Restrict network access to DDMC management interfaces to high-privileged users only.
Upgrade to DDOS 8.0 or LTS 7.13.1.0 (LTS 7.10.1.30 or LTS 7.7.5.40 are also fixed)
- 1. Identify the current Data Domain Operating System (DDOS) version by running 'ddos Version' or checking the DDMC interface.
- 2. Determine which upgrade path applies based on your current version (LTS to LTS, or to 8.0).
- 3. Schedule a maintenance window as upgrades require system downtime.
- 4. Download the appropriate upgrade image from Dell Support (www.dell.com/support) - either LTS 7.7.5.40, LTS 7.10.1.30, LTS 7.13.1.0, or 8.0 depending on your upgrade strategy.
- 5. Upload the upgrade file to the DD system using 'ddos upgrade <path-to-file>' or via DDMC.
- 6. Run pre-upgrade checks using 'ddos upgrade -n <file>' to validate the image.
- 7. Execute the upgrade using 'ddos upgrade -f <file>' or via DDMC.
- 8. Verify successful completion and new version with 'ddos Version'.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37138 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37138 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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