dbcve.org
Powerprotect Data ManagerApplication · Dell

CVE-2025-43888

HIGH · 7.8 CVSS v3.1 Published 2025-09-10
Fix available
A fix is available. Upgrade to 19.21 or later.
See remediation →
80/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 Manager, Hyper-V, version(s) 19.19 and 19.20, contain(s) an Insertion of Sensitive Information into Log File vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Unauthorized access.

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 Manager for Hyper-V versions 19.19 and 19.20 contains an Insertion of Sensitive Information into Log File vulnerability. A low-privileged local attacker could read log files to obtain sensitive information (likely credentials, tokens, or authentication data) that is being improperly logged, leading to unauthorized access to the system or data.

MitigationUpdate to a patched version when Dell releases a fix. In the interim, restrict access to log files, review existing logs for sensitive data exposure, and implement log sanitization to prevent future sensitive information leakage.

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
Powerprotect Data ManagerApplication
Affected:< 19.21

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Check installed PowerProtect Data Manager version
    Use the Dell PowerProtect Data Manager web UI or run 'dpm version' command via CLI to determine the installed version number
    Affected if Version is 19.19 or 19.20 (any version below 19.21)
  2. Locate log files
    Navigate to the Dell PowerProtect Data Manager log directory, typically found under the installation path or in /var/log/dpm/ on the appliance
    Affected if Log files exist and are accessible to the low-privileged user account
  3. Search logs for sensitive strings
    Use grep or similar tool to search log files for patterns like 'password', 'token', 'secret', 'key', 'credential', 'auth', 'bearer', or base64-encoded strings that may indicate exposed authentication data
    Affected if Log files contain any password, token, API key, or authentication-related strings in plain text
  4. Review recent log entries for credentials
    Examine the most recent log files (especially those from Hyper-V backup operations) for any plain-text credentials, session tokens, or authentication headers
    Affected if Recent logs contain any sensitive authentication information that should not be logged

You are affected if running PowerProtect Data Manager version 19.19 or 19.20 and log files contain exposed credentials, tokens, or authentication data that could be read by a low-privileged local user.

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 19.21 or later
Fixed in 19.21
Interim mitigation

Update to a patched version when Dell releases a fix. In the interim, restrict access to log files, review existing logs for sensitive data exposure, and implement log sanitization to prevent future sensitive information leakage.

Recommended fix High confidence

PowerProtect Data Manager 19.21

  1. Verify current PowerProtect Data Manager version is 19.19 or 19.20
  2. Download PowerProtect Data Manager version 19.21 from Dell support portal (support.dell.com)
  3. Review Dell upgrade documentation for PowerProtect Data Manager 19.21
  4. Execute upgrade procedure following Dell's recommended upgrade path
  5. Verify successful upgrade to version 19.21
  6. Confirm the vulnerability is resolved

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

Fix this in Powerprotect Data Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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