CVE-2022-29095
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 prior) and Dell SupportAssist Client Commercial versions (3.1.1 and prior) contain a cross-site scripting vulnerability. A remote unauthenticated malicious user could potentially exploit this vulnerability under specific conditions leading to execution of malicious code on a vulnerable 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.10.4 and prior, and Commercial versions 3.1.1 and prior) contains a stored or reflected cross-site scripting vulnerability in its web interface component. A remote unauthenticated attacker can inject malicious JavaScript code that executes in the context of the victim's browser when they interact with the vulnerable SupportAssist interface.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Verify Dell SupportAssist is installedCheck for SupportAssist installation directory, typically at C:\Program Files\Dell\SupportAssist or C:\Program Files (x86)\Dell\SupportAssist, or look for the SupportAssist entry in Programs and Features (Add/Remove Programs).Affected if SupportAssist Client is not installed on the system.
-
Determine installed versionOpen Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Dell\SupportAssist\Version (or check the About section in the SupportAssist application UI) and note the version number.Affected if Version is 3.10.4 or lower for Consumer editions, or 3.1.1 or lower for Commercial editions.
-
Check if web interface component is enabledOpen Windows Services console (services.msc) and look for 'SupportAssist' or 'Dell SupportAssist Service' service status. Also check if port 8884 or 8888 (common SupportAssist web ports) are listening via 'netstat -an | findstr 8884' or similar.Affected if The SupportAssist web service is running and accessible (listening on configured ports).
-
Inspect web interface for suspicious entriesReview SupportAssist logs in %ProgramData%\Dell\SupportAssist\Logs for any unusual script tags, JavaScript statements, or unexpected URL parameters in HTTP requests.Affected if Log entries contain encoded script tags or unusual JavaScript patterns in user-supplied fields.
-
Verify web interface is network accessibleFrom another machine on the same network, attempt to access http://TARGET_IP:8884 or the configured port to confirm the web interface responds.Affected if The SupportAssist web interface is reachable from network hosts (indicating broader attack surface).
A system is affected if Dell SupportAssist Consumer version 3.10.4 or earlier, or Commercial version 3.1.1 or earlier is installed with the web interface component enabled and accessible.
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 a patched version beyond 3.10.4 (Consumer) or 3.1.1 (Commercial). If immediate patching is not possible, restrict network access to the SupportAssist service and disable the vulnerable web component until the update can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29095 — 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-29095 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