Security Resilience

CVE-2023-28062

Dell Powerprotect Data Manager 19.10 … 19.12

Published
11 April 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0077 54th percentile
Risk Priority 65 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-28062 is a high-severity Incorrect Use of Privileged APIs (CWE-648) vulnerability in Dell Powerprotect Data Manager. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Dell PPDM versions 19.12, 19.11 and 19.10, contain an improper access control vulnerability. A remote authenticated malicious user with low privileges could potentially exploit this vulnerability to bypass intended access restrictions and perform unauthorized actions.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
T1011 Exfiltration Over Other Network Medium Exfiltration
Adversaries may attempt to exfiltrate data over a different network medium than the command and control channel.
T1012 Query Registry Discovery
Adversaries may interact with the Windows Registry to gather information about the system, configuration, and installed software.
T1018 Remote System Discovery Discovery
Adversaries may attempt to get a listing of other systems by IP address, hostname, or other logical identifier on a network that may be used for Lateral Movement from the current system.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-23375Same product: Dell Powerprotect Data Manager
CVE-2026-22268Same product: Dell Powerprotect Data Manager
CVE-2026-22267Same product: Dell Powerprotect Data Manager
CVE-2026-44276Same product: Dell Powerprotect Data Manager
CVE-2024-22445Same product: Dell Powerprotect Data Manager
CVE-2025-23376Same product: Dell Powerprotect Data Manager
CVE-2025-23377Same product: Dell Powerprotect Data Manager
CVE-2026-40714Same product: Dell Powerprotect Data Manager
CVE-2024-22454Same product: Dell Powerprotect Data Manager
CVE-2026-22266Same product: Dell Powerprotect Data Manager

Affected Assets

dell
powerprotect data manager
19.10, 19.11, 19.12

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.2
  • V6.4.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly enforce correct usage of privileged APIs during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Restricting privileged utility programs limits the exposure of privileged APIs to misuse.

degrades

Privileged access rights directly govern the correct use of privileged APIs and reduce misuse.

blocks

Secure development lifecycle includes API usage standards that can prevent incorrect privileged calls.

blocks

A.8.26 requires that security requirements (including access segregation) be identified during development or acquisition; it does not itself enforce, implement or assure correct use of privileged APIs, so the weakness can still be present and exploitable.

blocks

Secure architecture principles guide proper privilege separation and API usage.

prevents

Secure coding standards can enforce correct usage of privileged APIs.

References