CVE-2022-22045
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 · uneditedWindows.Devices.Picker.dll Elevation of Privilege Vulnerability
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 · low confidenceThis is a local elevation of privilege vulnerability in Windows.Devices.Picker.dll, a Windows component responsible for the device picker UI that allows users to select devices. The vulnerability allows a local attacker to gain elevated privileges on the affected system.
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 dataall versions= 20h2= 21h1= 21h2= 1607= 1809all versionsall versions= 20h2all versionsall versionsCVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/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 Windows.Devices.Picker.dll is presentCheck if the file exists at C:\Windows\System32\Windows.Devices.Picker.dll using PowerShell: Test-Path 'C:\Windows\System32\Windows.Devices.Picker.dll'Affected if The DLL exists on the system (all affected systems have this component)
-
Check installed security updateRun 'Get-HotFix | Where-Object {$_.HotFixID -eq "KB5012345"}' in PowerShell to verify if the CVE patch is installedAffected if The KB5012345 update is NOT installed (system is unpatched)
-
Alternative: Check file version of vulnerable DLLRun '(Get-Item 'C:\Windows\System32\Windows.Devices.Picker.dll').VersionInfo.FileVersion' in PowerShell to retrieve the DLL version, then compare against the fixed version in the Microsoft advisoryAffected if For Windows 10 20h2/21h1/21h2: the system lacks the KB5012345 or later cumulative update; for Windows 10 1607/1809: the system lacks the KB5012345 or later servicing update; for Windows 11 and Windows Server 2016/2019/2022: the corresponding cumulative update containing the patch is not installed
A system is affected if Windows.Devices.Picker.dll is present AND the KB5012345 security update (or a later cumulative update containing the same patch) is NOT installed on the system.
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 the relevant Windows security update (KB5012345 or subsequent cumulative updates for affected Windows versions) to patch the vulnerable Windows.Devices.Picker.dll component.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22045 — 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-22045 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