dbcve.org
Powerprotect Data ManagerApplication · Dell

CVE-2025-43725

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, Generic Application Agent, version(s) 19.19 and 19.20, contain(s) an Incorrect Default Permissions vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Code execution.

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 and Generic Application Agent versions 19.19 and 19.20 ship with overly permissive default file or directory permissions. A low-privileged local user can read, modify, or execute files they should not have access to, potentially enabling code execution with elevated privileges.

MitigationAudit and remediate file/directory permissions on affected installations to enforce least-privilege access controls, ensuring only authorized service accounts have write/execute access to critical components.

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. Identify installed PowerProtect Data Manager version
    Check the installed version using the Dell software inventory or package manager (e.g., rpm -q or dpkg -l for Linux, or check Add/Remove Programs on Windows). Look for version 19.19 or 19.20 specifically.
    Affected if Installed version is 19.19 or 19.20, or any version lower than 19.21
  2. Identify installed Generic Application Agent version
    Check the installed version of the Generic Application Agent component using the same methods as above (software inventory, package manager).
    Affected if Installed version is 19.19 or 19.20, or any version lower than 19.21
  3. Audit installation directory permissions
    Inspect permissions on the main installation directory (commonly /opt/dell/powerprotect or C:\Program Files\Dell\PowerProtect on Windows). Use 'ls -la' on Linux or icacls on Windows to check if non-privileged users have read, write, or execute access beyond what is least-privilege.
    Affected if Installation directory grants write or execute access to standard users or the Everyone/Users group
  4. Check configuration file permissions
    Locate configuration files in the installation directory and subdirectories. Verify permissions using 'ls -la' or icacls. Ensure only the service account and administrators can modify these files.
    Affected if Configuration files are readable or writable by low-privileged users or general user groups
  5. Verify service executable permissions
    Identify service executables and binaries in the installation path. Check that they are not world-writable or group-writable by non-admin users, as this could allow privilege escalation.
    Affected if Service binaries or executables are writable by non-privileged users or user groups like Everyone/Users

A user is affected if their installed version of Dell PowerProtect Data Manager or Generic Application Agent is 19.19 or 19.20 (or any version below 19.21) AND the installation directories, configurations, or binaries have overly permissive file permissions allowing low-privileged local users to read, modify, or execute them.

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

Audit and remediate file/directory permissions on affected installations to enforce least-privilege access controls, ensuring only authorized service accounts have write/execute access to critical components.

Recommended fix High confidence

PowerProtect Data Manager version 19.21 or later

  1. Upgrade PowerProtect Data Manager to version 19.21 or later to resolve the Incorrect Default Permissions vulnerability (CWE-276).
  2. After upgrade, verify that default file and directory permissions are correctly configured according to Dell best practices.
  3. Confirm that the low-privileged attacker cannot exploit default permission misconfigurations after the upgrade.

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

Fix this in Powerprotect Data Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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