CVE-2023-28062
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 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.
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 · high confidenceDell PowerProtect Data Manager (PPDM) versions 19.10-19.12 contain an improper access control vulnerability where low-privileged authenticated users can bypass intended security restrictions and perform actions reserved for higher-privilege roles. The vulnerability allows unauthorized access to functionality or data through improper validation of user 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.10= 19.11= 19.12CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 installed PPDM versionLog into the Dell PowerProtect Data Manager web interface and navigate to the About or Settings page to view the software version. Alternatively, use the command-line interface (if available) to query the version using 'dpadm --version' or consult the installation directory for version files.Affected if The installed version is 19.10, 19.11, or 19.12.
-
Verify presence of low-privilege accountsAccess the User Management or Administration section in the PPDM web interface to list all configured users and their assigned roles. Identify any accounts assigned to roles below administrator-level privileges.Affected if There are authenticated users with non-administrative roles in the system.
-
Review audit logs for privilege escalation eventsNavigate to the Audit Logs or Security Logs section within PPDM. Search for events where low-privilege users performed actions typically reserved for higher-privilege roles, such as administrative configurations, data restores, or system modifications.Affected if Audit logs show low-privilege users executing actions outside their assigned role permissions.
-
Inspect access control configurationExamine the Role-Based Access Control (RBAC) settings in PPDM to verify that permission boundaries between roles are properly enforced. Check if there are any misconfigurations allowing role privilege escalation.Affected if Access control policies allow low-privilege users to access higher-privilege functions or data.
You are affected if your PPDM version is 19.10, 19.11, or 19.12 AND low-privilege users exist who could potentially bypass role restrictions.
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 · scopedApply the vendor-supplied patch from Dell for the specific PPDM version in use, then validate that access controls are properly enforced for all privilege levels.
Upgrade to PowerProtect Data Manager version 19.13 or later (the next release after the affected 19.10-19.12 versions)
- Log into the Dell Support website and locate the PowerProtect Data Manager security advisory for CVE-2023-28062
- Download the patched version of PowerProtect Data Manager as indicated in the security advisory
- Back up the current PowerProtect Data Manager configuration and database following Dell best practices
- Follow the standard PowerProtect Data Manager upgrade procedure documented in the Dell upgrade guide
- After upgrade, verify that the version matches the patched release and confirm all services are running properly
- Validate that the access control vulnerability is resolved by testing low-privilege user access restrictions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28062 — 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-2023-28062 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