dbcve.org
Command \| MonitorApplication · Dell

CVE-2023-28068

HIGH · 7.8 CVSS v3.1 Published 2023-05-05
Fix available
A fix is available. Upgrade to after 10.9 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 Command Monitor, versions 10.9 and prior, contains an improper folder permission vulnerability. A local authenticated malicious user can potentially exploit this vulnerability leading to privilege escalation by writing to a protected directory when Dell Command Monitor is installed to a non-default path

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 Command Monitor versions 10.9 and prior has improper folder permission configuration when installed to non-default paths. A local authenticated user can write to protected directories due to overly permissive access controls, enabling privilege escalation.

MitigationApply vendor-supplied patch or update to Dell Command Monitor beyond version 10.9. If patching is not immediately possible, audit and restrict folder permissions on non-default installations to follow least-privilege principles.

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
Command \| MonitorApplication
Affected:<= 10.9

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. Check if Dell Command Monitor is installed and identify its version
    Open Windows Control Panel > Programs and Features, or run 'wmic product get name,version' in Command Prompt, and look for 'Dell Command Monitor' to retrieve the installed version number
    Affected if Version is 10.9 or lower (any version <= 10.9)
  2. Locate the Dell Command Monitor installation directory
    Right-click the program in Programs and Features and select Properties, or check the installation path in the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the InstallLocation value
    Affected if Installation path is present and version is <= 10.9
  3. Determine if installation path is non-default
    Compare the identified installation path against the standard default paths (typically C:\Program Files\Dell\Command Monitor or C:\Program Files (x86)\Dell\Command Monitor)
    Affected if Installation path differs from the default Program Files location (installed to a custom or non-standard directory)
  4. Inspect folder permissions on the installation directory
    Right-click the installation folder > Properties > Security tab, or run 'icacls "<installation_path>"' in Command Prompt, and examine the access control entries for each user group
    Affected if Authenticated users, Users group, or non-admin accounts have Write or Full Control permissions on the installation directory or its subfolders

A user is affected if Dell Command Monitor version 10.9 or lower is installed to a non-default path with overly permissive folder permissions allowing write access to standard user accounts.

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 a release after 10.9
Interim mitigation

Apply vendor-supplied patch or update to Dell Command Monitor beyond version 10.9. If patching is not immediately possible, audit and restrict folder permissions on non-default installations to follow least-privilege principles.

Recommended fix Moderate confidence

Dell Command Monitor version 10.10 or later (latest available version from Dell support)

  1. Navigate to www.dell.com and locate the Dell Command Monitor support page
  2. Download the latest version of Dell Command Monitor available for your operating system
  3. Before uninstalling the current version, document any custom configurations
  4. Uninstall the current version of Dell Command Monitor (versions 10.9 and prior)
  5. Install the new version of Dell Command Monitor
  6. Restore any documented custom configurations
  7. Verify the installation was successful and the application runs normally
  8. Confirm folder permissions are correctly set on the installation directory
Caveat Ensure any custom configurations or integrations with Dell Command Monitor are compatible with the new version before production deployment

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

Fix this in Command \| Monitor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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