CVE-2022-29093
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 vulnerability. Authenticated non-admin user could exploit the issue and delete 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; commercial versions 3.1.1 and prior) contains an arbitrary file deletion vulnerability. An authenticated non-privileged user can exploit insufficient access controls in the application to delete arbitrary files on the filesystem, potentially leading to privilege escalation or denial of service.
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.
-
Identify if Dell SupportAssist Client is installedOpen Windows Settings > Apps & Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs. Look for 'Dell SupportAssist' or 'Dell SupportAssist for Home Pcs' or 'Dell SupportAssist for Business Pcs'.Affected if Dell SupportAssist Client appears in the installed programs list.
-
Determine the installed version of Dell SupportAssistOnce identified as installed, note the version shown in the Programs list or retrieve via PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*SupportAssist*'} | Select-Object DisplayName, DisplayVersion.Affected if A version number is returned that matches the product name.
-
Identify the product edition (Home or Business)Compare the product name from step 1 or registry entry to determine if it is the Home Pcs or Business Pcs edition. The Business version typically shows 'SupportAssist for Business Pcs' or similar commercial naming.Affected if The product is identified as either 'Dell SupportAssist for Home Pcs' or 'Dell SupportAssist for Business Pcs'.
-
Compare installed version against vulnerable rangesIf Home edition: Check if version is 3.10.4 or lower. If Business edition: Check if version is 3.1.1 or lower. For example, a version like 3.10.3 or 3.1.0 would be vulnerable.Affected if The installed version is 3.10.4 or lower (Home) OR 3.1.1 or lower (Business).
-
Verify the service is present and runningOpen Services (services.msc) or run 'Get-Service | Where-Object {$_.DisplayName -like '*SupportAssist*'}' in PowerShell. Confirm the Dell SupportAssist service exists.Affected if The SupportAssist service exists on the system, indicating the application is deployed and potentially in use.
A user is affected if Dell SupportAssist Client (Home edition version 3.10.4 or lower, or Business edition version 3.1.1 or lower) 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 dataApply vendor-supplied patches from Dell. Update SupportAssist Client to a version beyond the vulnerable releases (consumer: >3.10.4; commercial: >3.1.1). Verify the update in a non-production environment before deployment.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29093 — 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-29093 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