CVE-2025-43887
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 Data Manager, version(s) 19.19 and 19.20, Hyper-V contain(s) an Incorrect Default Permissions vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of privileges.
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 Data Manager versions 19.19 and 19.20 contain an incorrect default permissions vulnerability in the Hyper-V component. A low-privileged local attacker could exploit this misconfigured permissions to gain elevated privileges on the system.
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< 19.21CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify PowerProtect Data Manager versionUse the Dell product version checking mechanism (typically via the management console, installed software listing, or 'about' section in the product UI) to determine the exact installed version numberAffected if Version is 19.19 or 19.20 (any version prior to 19.21)
-
Confirm Hyper-V component is configuredCheck whether the Hyper-V backup/recovery component is enabled or deployed in the PowerProtect Data Manager environment. This may be visible in the product's component list, protection policies, or infrastructure settingsAffected if Hyper-V component is present and active in the installation
-
Examine Hyper-V component file permissionsLocate the directories or files associated with the Hyper-V component within the PowerProtect Data Manager installation path. Use operating system tools (such as 'icacls' on Windows or 'ls -la' on Linux) to inspect the access control list permissions on these objectsAffected if Low-privileged users or 'Everyone' group have excessive permissions (such as Full Control or Write) on Hyper-V component files or directories
-
Review service account and role assignmentsCheck the user roles and service account assignments within PowerProtect Data Manager, specifically looking at permissions granted for Hyper-V backup operations to standard (non-admin) usersAffected if Standard users have been granted elevated or administrative roles related to Hyper-V operations
-
Audit local user group membershipsExamine local system user groups on the PowerProtect Data Manager server to identify whether any low-privileged accounts have been added to privileged groups (such as Administrators or Backup Operators)Affected if Standard user accounts have elevated group memberships that should not be present
You are affected if PowerProtect Data Manager version is 19.19 or 19.20 AND the Hyper-V component is configured, with default permissions allowing low-privileged users elevated access.
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 · scoped19.21
Apply the vendor patch or remediate the default permissions on the affected Hyper-V component to restrict unnecessary elevated access from low-privileged users.
19.21 or later
- 1. Back up all critical data and configurations on the PowerProtect Data Manager system
- 2. Download Dell PowerProtect Data Manager version 19.21 or later from Dell's support website
- 3. Review the upgrade guide specific to your deployment (Hyper-V)
- 4. Execute the upgrade procedure according to Dell's official documentation
- 5. Verify the upgrade completed successfully
- 6. Confirm the default permissions have been corrected by reviewing system permissions
- 7. Test that the system functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43887 — 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-2025-43887 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