CVE-2022-22037
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 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 confidenceThis is a Windows kernel-level Elevation of Privilege vulnerability in the Advanced Local Procedure Call (ALPC) mechanism. ALPC is an inter-process communication facility used extensively within Windows for communication between processes, including system services. The vulnerability allows a local attacker to elevate their privileges, potentially from a low-privilege user to SYSTEM or equivalent high-privilege context.
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 versionsall versionsall versionsall versions= r2all versions= r2all versions= 20h2CVSS 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
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows version and build numberAffected if The version matches any of the affected products: Windows 10 (all versions, 1607, 1809, 20h2, 21h1, 21h2), Windows 11 (all versions), Windows 7 (all versions), Windows 8.1 (all versions), Windows RT 8.1, Windows Server 2008/2008 R2 (all versions), Windows Server 2012/2012 R2 (all versions), Windows
-
Verify security update presenceCheck the installed Windows updates by running 'wmic qfe list' or viewing the update history in Settings > Windows Update > Update history. Look for the security update addressing CVE-2022-22037Affected if The security update for CVE-2022-22037 is NOT installed on the system
-
Confirm local user contextRun 'whoami /all' to see your current user context and group memberships. Check if you are running as a standard user or non-administrative accountAffected if You are running as a standard (non-administrative) local user and the system is unpatched, the vulnerability could allow privilege escalation to SYSTEM
-
Review ALPC-related audit eventsOpen Event Viewer and navigate to Security logs. Filter for Event ID 4656 (Object Handle Requested) or 4663 (Object Access Attempted) targeting ALPC endpoints under \BaseNamedObjects\ and \KnownDlls\Affected if Unusual or excessive ALPC handle requests from low-privilege processes are observed, potentially indicating exploitation attempts
A system is affected if it runs any of the listed Windows versions AND lacks the CVE-2022-22037 security update, allowing a local low-privilege user to potentially escalate to SYSTEM privileges through ALPC.
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 appropriate Microsoft security updates for CVE-2022-22037 to all affected Windows systems. Prioritize domain controllers and systems with sensitive data or privileged access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22037 — 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-22037 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