CVE-2022-29094
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.10.4 and versions prior) and Dell SupportAssist Client Commercial versions (3.1.1 and versions prior) contain an arbitrary file deletion/overwrite vulnerability. Authenticated non-admin user could exploit the issue and delete or overwrite arbitrary files on 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 · high confidenceDell SupportAssist Client Consumer (versions 3.10.4 and prior) and Commercial (versions 3.1.1 and prior) contain an arbitrary file deletion/overwrite vulnerability. An authenticated non-admin user can exploit this local vulnerability to delete or overwrite arbitrary files on the system, potentially leading to privilege escalation or system compromise.
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.1.1<= 3.10.4CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Locate Dell SupportAssist installationCheck for SupportAssist installation in typical locations: %ProgramFiles%\Dell\SupportAssist, %ProgramFiles(x86)%\Dell\SupportAssist, or C:\Program Files\Dell\SupportAssist. Also check the Windows Programs and Features list.Affected if Dell SupportAssist Consumer or Commercial software is installed on the system
-
Determine installed versionRight-click the SupportAssist.exe file in the installation directory, select Properties, then view the Details tab for the Version field. Alternatively, open SupportAssist and navigate to the About or Settings section to view the version number.Affected if The displayed version is 3.10.4 or earlier for Consumer, or 3.1.1 or earlier for Commercial
-
Identify SupportAssist variantCheck whether the installation is the Consumer or Commercial version. Consumer typically ships with Dell consumer PCs; Commercial is often deployed in enterprise environments. Check the program name in Programs and Features or the About section within the application.Affected if The installed variant is Consumer version <= 3.10.4 or Commercial version <= 3.1.1
-
Verify user access contextThe vulnerability requires an authenticated non-admin user. Check if SupportAssist runs with elevated privileges while a low-privilege user account has write access to the installation directory. Review folder permissions on the SupportAssist directory.Affected if Non-admin users have write permissions to the SupportAssist installation directory or related configuration folders
The system is affected if Dell SupportAssist Consumer version 3.10.4 or earlier, or Commercial version 3.1.1 or earlier, is installed and non-admin users have access to modify files in the installation directory.
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 dataUpgrade Dell SupportAssist Client to version 3.10.5 or later (Consumer) or version 3.1.2 or later (Commercial). If patching is not immediately possible, restrict low-privilege user access to the SupportAssist installation directory and monitor for suspicious file operations.
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29094 — 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-29094 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