CVE-2022-34384
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 (version 3.11.1 and prior), SupportAssist Client Commercial (version 3.2 and prior), Dell Command | Update, Dell Update, and Alienware Update versions before 4.5 contain a Local Privilege Escalation Vulnerability in the Advanced Driver Restore component. A local malicious user may potentially exploit this vulnerability, leading to privilege escalation.
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 confidenceLocal privilege escalation vulnerability in the Advanced Driver Restore component of Dell SupportAssist, Dell Command | Update, Dell Update, and Alienware Update. A local malicious user can exploit improper access controls in the driver restore functionality to gain elevated system privileges.
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< 4.5.0< 4.5.0<= 3.2.0<= 3.11.2< 4.5.0CVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.
-
Identify installed Dell update softwareCheck installed programs via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look in Program Files for Dell folders (Dell SupportAssist, Dell Update, Dell Command Update, Alienware Update)Affected if Any of these Dell applications are installed
-
Determine installed version of Dell softwareRight-click the executable (e.g., DellUpdate.exe, DellCommandUpdate.exe, SupportAssist.exe, AlienwareUpdate.exe), select Properties, and check the File Version field. Alternatively, check the Uninstall registry key for the DisplayVersion valueAffected if Version is below 4.5.0 for Dell Update/Dell Command Update/Alienware Update, below 3.11.2 for SupportAssist Home, or below/equal to 3.2.0 for SupportAssist Business
-
Verify Advanced Driver Restore component existsLook for Dell driver restore related files or services. Check Program Files for Dell\DriverRestore or similar folders, or search for 'DriverRestore' in Windows ServicesAffected if Advanced Driver Restore component is present on the system
-
Check if driver restore has been runReview application logs in %ProgramData%\Dell or %AppData%\Dell for entries containing 'DriverRestore', 'RestoreDriver', or similar driver restore activityAffected if Driver restore functionality has been executed on the system
User is affected if any Dell SupportAssist, Dell Command Update, Dell Update, or Alienware Update version is installed that is below the patched thresholds AND the Advanced Driver Restore component is present or has been used.
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 · scoped4.5.0
Update affected Dell software to patched versions: SupportAssist Client Consumer to version 3.11.2 or later, SupportAssist Client Commercial to version 3.3 or later, and Dell Command | Update/Dell Update/Alienware Update to version 4.5 or later.
Version 4.5.0 or later for Alienware Update, Command Update, Dell Update, and Update; version 4.5.0 or later for SupportAssist Consumer and Commercial
- Identify which Dell application is installed: Alienware Update, Command Update, Dell Update, or SupportAssist (Consumer or Commercial)
- Check the current version of the installed application through Add/Remove Programs or the application's About section
- Download Dell Update, Alienware Update, Command Update, or SupportAssist version 4.5.0 or later from the official Dell support website (dell.com)
- Close the running instance of the application if prompted
- Run the downloaded installer to upgrade to version 4.5.0 or later
- Restart the system if required and verify the new version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34384 — 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-34384 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