CVE-2022-23283
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 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 an elevation of privilege vulnerability in Windows Advanced Local Procedure Call (ALPC), a kernel-mode inter-process communication mechanism. The flaw allows a local attacker to escalate privileges from a standard user to higher-level SYSTEM or administrator access by exploiting improper validation in ALPC message handling.
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= 1809= 1909all versionsall versionsall versionsall versions= 20h2= 2022all versions= r2all versions= r2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows version and buildRun 'winver' or 'systeminfo' from command prompt, or run 'Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber' in PowerShellAffected if The version and build number match any of the affected products listed (Windows 10 versions 20h2/21h1/21h2/1607/1809/1909, Windows 11 all versions, Windows 7 all versions, Windows 8.1 all versions, Windows Rt 8.1, Windows Server 20h2/2022, Windows Server 2008 all versions/r2, Windows Server 2012 all
-
Verify security update is installedOpen Control Panel > Programs > Programs and Features > View installed updates, or run 'Get-HotFix' in PowerShell to list installed hotfixesAffected if The security update for CVE-2022-23283 (KB5011543 or later cumulative update) is NOT installed - this means the system is still vulnerable
If you are running any affected Windows version and the corresponding security patch is not installed, your environment is vulnerable to local privilege escalation via 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.
dbcve · scopedApply the relevant Microsoft security patch for this vulnerability as part of regular patch management. Prioritize patching systems where untrusted users have local access.
- Open Windows Update by clicking Start > Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Restart your computer after the updates are installed
- Alternatively, manually download and install the specific security update for your Windows version from the Microsoft Update Catalog - search for KB5010342 (February 2022 security updates)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23283 — 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-23283 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