CVE-2022-29092
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 SupportAssist Client Consumer versions (3.11.0 and versions prior) and Dell SupportAssist Client Commercial versions (3.2.0 and versions prior) contain a privilege escalation vulnerability. A non-admin user can exploit the vulnerability and gain admin access to 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 confidenceDell SupportAssist Client (both Consumer versions 3.11.0 and prior, and Commercial versions 3.2.0 and prior) contains a privilege escalation vulnerability allowing non-administrative users to gain administrator-level system access. The specific attack vector and technical mechanism are not detailed in the available description.
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<= 3.2.0<= 3.11.0CVSS 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.
-
Confirm Dell SupportAssist Client is installedOpen Windows Control Panel or Settings > Apps & Features and search for 'SupportAssist', or run 'Get-Package -ProviderName Programs -IncludeOptionalPrograms | Where-Object {$_.Name -like "*SupportAssist*"}' in PowerShellAffected if Dell SupportAssist Client appears in the installed programs list
-
Identify the installed version numberIn Programs and Features, click on Dell SupportAssist and view the Version, or check the version in the application's About/Help section. Alternatively, examine the file properties of the main executable (typically in C:\Program Files\Dell\SupportAssist\ or C:\Program Files (x86)\Dell\SupportAssist\)Affected if The version displayed is 3.11.0 or earlier for Consumer editions, or 3.2.0 or earlier for Commercial editions
-
Determine the SupportAssist edition typeCheck the product name in Add/Remove Programs or the application's UI to distinguish between 'SupportAssist for Home PCs' (Consumer) and 'SupportAssist for Business PCs' (Commercial)Affected if The installed product is either Dell SupportAssist for Home PCs version 3.11.0 or prior, OR Dell SupportAssist for Business PCs version 3.2.0 or prior
A user is affected if Dell SupportAssist Client (either Consumer version 3.11.0 and prior, or Commercial version 3.2.0 and prior) is installed on their system.
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 dataUpdate Dell SupportAssist Client to a version newer than 3.11.0 (Consumer) or 3.2.0 (Commercial) once patches are available from Dell. Restrict or monitor access to SupportAssist functionality for non-admin users until patched.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29092 — 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-2022-29092 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