dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-41045

HIGH · 7.8 CVSS v3.1 Published 2022-11-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Windows Advanced Local Procedure Call (ALPC) 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 · moderate confidence

This is a Windows kernel-level vulnerability in the Advanced Local Procedure Call (ALPC) subsystem. ALPC is an inter-process communication mechanism used extensively by Windows system components. The vulnerability allows a local attacker to elevate their privileges, potentially gaining SYSTEM or kernel-level access on the affected machine.

MitigationApply the Microsoft security update for CVE-2022-41045 as soon as possible. Prioritize domain controllers and systems with high privilege access requirements.

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
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 22h2= 1607= 1809
Windows 11Operating system
Affected:all versions= 22h2
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the installed Windows version and build number
    Affected if The version and build number fall within the affected ranges (Windows 10 versions 1607, 1809, 20h2, 21h1, 21h2, 22h2; Windows 11 version 22h2; Windows 7 all versions; Windows 8.1 all versions; Windows RT 8.1 all versions; Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016 all versions) and the securi
  2. Check if the CVE-2022-41045 security update is installed
    Open Control Panel > Programs > Programs and Features > View installed updates, or run 'wmic qfe list' to list installed hotfixes. Look for the security update corresponding to CVE-2022-41045 (typically a Windows Security update from October 2022 or later)
    Affected if The security update for CVE-2022-41045 is NOT installed on the system
  3. Verify kernel patch status via PowerShell
    Run 'Get-HotFix -Description "Security Update" | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security updates
    Affected if No security update from October 2022 or later for the Windows kernel is present, indicating the patch is missing
  4. Confirm ALPC component version (if accessible)
    Check the ALPC system component by examining the Windows kernel version: run 'ver' at command prompt or check file version of ntoskrnl.exe at C:\Windows\System32\ntoskrnl.exe
    Affected if The kernel file version predates the October 2022 security updates that address CVE-2022-41045

A system is affected if it runs any of the affected Windows versions listed AND lacks the corresponding security update for CVE-2022-41045.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update for CVE-2022-41045 as soon as possible. Prioritize domain controllers and systems with high privilege access requirements.

Recommended fix High confidence
  1. Open Windows Update by clicking the Start button and selecting Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. If automatic updates are not enabled, ensure 'Automatic (Recommended)' is selected under Advanced options
  4. After updates are installed, restart your computer if prompted
  5. Verify the update was installed by checking Windows Update history for the November 2022 security updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41045 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41045 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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