CVE-2022-34392
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 · uneditedSupportAssist for Home PCs (versions 3.11.4 and prior) contain an insufficient session expiration Vulnerability. An authenticated non-admin user can be able to obtain the refresh token and that leads to reuse the access token and fetch 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 · high confidenceDell SupportAssist for Home PCs (versions 3.11.4 and prior) fails to properly expire sessions. An authenticated non-admin user can obtain the refresh token and reuse it to generate new access tokens, bypassing session expiration and gaining continued unauthorized access to sensitive information.
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.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 Dell SupportAssist for Home PCs versionOpen Windows Settings > Apps > Apps & Features, locate 'Dell SupportAssist' and note the version number displayed, or run 'Get-Package -Name "*SupportAssist*" | Select-Object Name,Version' in PowerShellAffected if The displayed version is 3.11.4 or any version lower than 3.11.4
-
Check SupportAssist version via RegistryRun 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*SupportAssist*"} | Select-Object DisplayName,DisplayVersion' in PowerShellAffected if The DisplayVersion value is 3.11.4 or lower
-
Verify token expiration behaviorMonitor network traffic or application logs during a session timeout scenario - attempt to use a refresh token after the declared session timeout period to see if it still grants accessAffected if The refresh token remains valid and generates a new access token after the expected session expiration time has passed
You are affected if Dell SupportAssist for Home PCs is installed at version 3.11.4 or prior, and refresh tokens continue to work beyond their intended expiration window.
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.
dbcve · scopedImplement proper token expiration by invalidating refresh tokens after single use or after a defined time-to-live, and enforce session timeout to prevent token reuse.
SupportAssist for Home PCs version > 3.11.4 (contact Dell for exact fixed version)
- Contact Dell Support or visit Dell's official SupportAssist download page to obtain the latest version of SupportAssist for Home PCs
- Ensure you back up any critical data before updating the software
- Download and install the version newer than 3.11.4 from Dell's official website
- After upgrade, verify that session tokens properly expire and cannot be reused
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34392 — 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-34392 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