CVE-2025-23375
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 Reporting, version(s) 19.17, contain(s) an Incorrect Use of Privileged APIs 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 Reporting version 19.17 contains an incorrect use of privileged APIs vulnerability that allows a low-privileged local attacker to escalate privileges. The vulnerability stems from improper handling or authorization when calling privileged system APIs from the reporting component, enabling privilege escalation beyond the attacker's assigned permissions.
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.17CVSS 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.
-
Verify PowerProtect Data Manager is installedCheck for the presence of Dell PowerProtect Data Manager on the system. Common installation paths include C:\Program Files\Dell\PowerProtect or /opt/dell/powerprotect. Check Windows Services or Linux service manager for 'PowerProtect Data Manager' service.Affected if Dell PowerProtect Data Manager software is installed on the system
-
Confirm the Reporting component is presentInspect the installation directory for the reporting component. Look for subdirectories or modules named 'reporting', 'reports', or similar. On Windows, check Program Files for Dell PowerProtect Data Manager Reporting. On Linux, check /opt/dell/powerprotect/reporting or similar paths.Affected if The reporting component module or service exists on the system
-
Determine the installed versionLocate version information in the installation. Check for a version file,About dialog, or use command line: dpkg -l | grep -i powerprotect (Debian/RHEL), rpm -qa | grep -i powerprotect, or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Dell\PowerProtect Data Manager. Alternatively, examine the reporting module's properties or manifest file.Affected if The installed version is exactly 19.17 (this specific version is affected)
-
Check for local user contextIdentify the user context running the reporting service. On Windows, check the service properties in Services.msc for PowerProtect Data Manager Reporting service logon account. On Linux, use 'ps aux | grep -i reporting' to find the process and check its user ownership.Affected if The reporting component runs with elevated privileges and lower-privileged local users have access to the system
The system is affected if Dell PowerProtect Data Manager with the reporting component is installed and the version is exactly 19.17, as this specific version contains the vulnerable privileged API handling.
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.
From vendor dataApply vendor-provided patch or update to Dell PowerProtect Data Manager Reporting version 19.17. If no patch is available, restrict local access to trusted personnel and monitor for suspicious process execution or privilege changes.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23375 — 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-23375 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