Supportassist For Business PcsApplication · Dell

CVE-2022-34387

HIGH · 7.8 CVSS v3.1 Published 2023-02-11
Fix available
A fix is available. Upgrade to after 3.11.4 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 SupportAssist for Home PCs (version 3.11.4 and prior) and SupportAssist for Business PCs (version 3.2.0 and prior) contain a privilege escalation vulnerability. A local authenticated malicious user could potentially exploit this vulnerability to elevate privileges and gain total control of the system.

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 SupportAssist contains a local privilege escalation vulnerability allowing an authenticated user to gain SYSTEM-level or full administrative control of the affected Windows system. The vulnerability exists in versions 3.11.4 and prior for Home PCs and 3.2.0 and prior for Business PCs.

MitigationUpdate to a patched version of Dell SupportAssist if available; otherwise, remove or disable the software until a patch can be applied.

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
Supportassist For Business PcsApplication
Affected:<= 3.2.0
Supportassist For Home PcsApplication
Affected:<= 3.11.4

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. Confirm Dell SupportAssist is installed
    Open Programs and Features in Control Panel or use 'Get-ItemProperty' in PowerShell to query the registry under HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'SupportAssist', or run 'wmic product get name,version' to list installed software.
    Affected if Dell SupportAssist is not present on the system, the vulnerability does not apply.
  2. Identify the SupportAssist variant
    Review the software name in Programs and Features or the uninstall registry entry. Look for 'Dell SupportAssist for Business PCs' or 'Dell SupportAssist for Home PCs' in the displayed name.
    Affected if The variant must be identified to apply the correct version threshold.
  3. Retrieve the installed version number
    In Programs and Features, note the version column for the SupportAssist entry. Alternatively, run 'wmic product where "name like '%SupportAssist%'" get name,version' or check the Uninstall registry key for the Version value.
    Affected if The version number is required to determine if it falls within the affected range.
  4. Compare version against affected ranges
    For Business PCs: check if version is <= 3.2.0. For Home PCs: check if version is <= 3.11.4. If the exact version cannot be determined, inspect the program's About or Help section within the application.
    Affected if Version <= 3.2.0 for Business PCs or <= 3.11.4 for Home PCs indicates the system is affected by this privilege escalation vulnerability.

The system is affected if Dell SupportAssist is installed and the installed version falls within the vulnerable ranges (3.2.0 and prior for Business PCs, 3.11.4 and prior for Home PCs).

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.

From vendor data
Upgrade available Upgrade to a release after 3.11.4
Interim mitigation

Update to a patched version of Dell SupportAssist if available; otherwise, remove or disable the software until a patch can be applied.

Fix this in Supportassist For Business Pcs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34387 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34387 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