CVE-2022-34388
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 information disclosure vulnerability. A local malicious user with low privileges could exploit this vulnerability to view and modify sensitive information in the database of the affected application.
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 and Business PCs contains an information disclosure vulnerability where a low-privilege local user can view and modify sensitive information in the application's database. This indicates improper access control on database files or database query handling, allowing privilege escalation through direct database access.
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
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Check installed SupportAssist versionOpen Windows Control Panel or Settings > Apps & Features, locate Dell SupportAssist (either for Home PCs or Business PCs), and note the displayed version number. Alternatively, open SupportAssist and look in the About or Help section for the version info.Affected if The version is 3.2.0 or lower for Business PCs, or 3.11.4 or lower for Home PCs.
-
Locate SupportAssist database filesSearch the filesystem for SQLite database files associated with SupportAssist. Common locations include: %ProgramData%\Dell\SupportAssist, %ProgramFiles%\Dell\SupportAssist, or the user's AppData folder. Look for files with .db, .sqlite, or .sqlite3 extensions named similarly to supportassist.db, sa.db, or similar.Affected if Database files exist in accessible directories.
-
Check file permissions on database filesRight-click each identified database file, select Properties > Security, and review the permissions. Use icacls or Get-Acl in PowerShell to list all users/groups with read or write access to the file.Affected if Users other than Administrators or SYSTEM have been granted read or write permissions to the database files.
-
Verify low-privilege user accessCreate a test standard user account (or use an existing non-admin account), log in as that user, and attempt to navigate to and open the SupportAssist database files using a SQLite viewer or command-line tool.Affected if A low-privilege (non-admin) user can successfully open, read, or modify the database files.
You are affected if you are running an affected version (SupportAssist for Business PCs <= 3.2.0 or for Home PCs <= 3.11.4) AND low-privilege users can access or modify the application's database files.
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: upgrade Dell SupportAssist for Home PCs to version 3.11.5 or later, and for Business PCs to version 3.2.1 or later. Alternatively, enforce strict file system permissions on the SupportAssist database files to prevent unauthorized low-privilege access.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34388 — 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-34388 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