CVE-2022-34386
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 for Home PCs (version 3.11.4 and prior) and SupportAssist for Business PCs (version 3.2.0 and prior) contain cryptographic weakness vulnerability. An authenticated non-admin user could potentially exploit the issue and obtain sensitive information.
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 for Home PCs (3.11.4 and prior) and Business PCs (3.2.0 and prior) contains a cryptographic weakness that allows authenticated non-admin users to obtain sensitive information. The vulnerability likely involves improper implementation of encryption, key management, or cryptographic operations that enables privilege escalation through a local attack vector.
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.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installed SupportAssist productCheck whether Dell SupportAssist for Home PCs or Dell SupportAssist for Business PCs is installed on the system. Look in Programs and Features or the installed applications list.Affected if Either product is installed and the version is at or below 3.11.4 for Home PCs or at or below 3.2.0 for Business PCs
-
Check SupportAssist versionLocate the installed version of SupportAssist. This is typically found in the application properties, about section, or Windows registry under HKLM\SOFTWARE\Dell\SupportAssist or HKLM\SOFTWARE\WOW6432Node\Dell\SupportAssist.Affected if The version number is 3.11.4 or lower (Home PCs) or 3.2.0 or lower (Business PCs)
-
Verify user account configurationReview local or domain user accounts on the system to confirm whether non-admin user accounts exist with access to the system.Affected if Non-admin authenticated users are present on the system who could potentially exploit this vulnerability
-
Confirm SupportAssist authentication is enabledCheck if SupportAssist authentication is configured to allow non-administrator users to log in or access the application.Affected if SupportAssist permits authentication by non-admin users, which is the prerequisite condition for this vulnerability to be exploitable
The environment is affected if Dell SupportAssist for Home PCs version 3.11.4 or below or for Business PCs version 3.2.0 or below is installed and non-administrator users have authenticated access to the application.
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 patches when released. In the interim, restrict SupportAssist access to admin-only users and monitor for unauthorized access attempts by lower-privileged accounts.
- 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-34386 — 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-34386 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