dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-30224

HIGH · 7.0 CVSS v3.1 Published 2022-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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 local Elevation of Privilege vulnerability in Windows Advanced Local Procedure Call (ALPC), an inter-process communication mechanism. The flaw allows a locally authenticated attacker to escalate privileges, potentially executing code at higher privilege levels (such as SYSTEM) by manipulating ALPC message handling.

MitigationApply the relevant Microsoft security update for this vulnerability through Windows Update or manual patch deployment. Prioritize patching domain controllers and servers given the local privilege escalation risk.

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= 1607= 1809
Windows 11Operating system
Affected:all versions
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= 20h2

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Identify Windows version and build
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows edition, version, and build number
    Affected if The version matches any of the affected releases: Windows 10 (all versions including 20h2, 21h1, 21h2, 1607, 1809), Windows 11 (all versions), Windows 7 (all versions), Windows 8.1 (all versions), Windows Rt 8.1, Windows Server 2008 (all versions including R2), Windows Server 2012 (all versions incl
  2. Check for security update installation
    Run 'wmic qfe list' or 'Get-HotFix' in PowerShell to list installed security updates. Search for the update corresponding to CVE-2022-30224 (typically a monthly security update from 2022)
    Affected if The security update for CVE-2022-30224 is NOT installed, indicating the system is unpatched for this vulnerability
  3. Verify ALPC is present
    ALPC is a core Windows inter-process communication mechanism. Confirm it exists by checking for the presence of %SystemRoot%\System32\alpc*.dll files or verifying the ALPC subsystem via process viewer
    Affected if ALPC is a built-in Windows component present on all affected systems; its absence would be extremely unusual and likely indicates a severely modified or non-standard system

A system is affected if it runs any of the listed Windows versions and is missing the CVE-2022-30224 security update, as exploitation requires no special configuration beyond being a local authenticated user on an unpatched Windows host.

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 relevant Microsoft security update for this vulnerability through Windows Update or manual patch deployment. Prioritize patching domain controllers and servers given the local privilege escalation risk.

Recommended fix Moderate confidence
  1. Ensure Windows Update is enabled and configured to automatically receive security updates
  2. Check for updates via Settings > Update & Security > Windows Update or the Control Panel
  3. Locate and install the security update addressing CVE-2022-30224 (refer to Microsoft Security Response Center at msrc.microsoft.com for the specific KB article number for your Windows version)
  4. After installation, restart the affected system to complete the patch deployment
  5. Verify the patch was successfully applied by checking Windows Update history or using the System Information tool

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30224 — 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-30224 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