dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-24549

HIGH · 7.8 CVSS v3.1 Published 2022-04-15
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 AppX Package Manager 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 Elevation of Privilege vulnerability in the AppX Package Manager (used for managing Windows Store apps and app packages). The flaw allows a low-privilege authenticated user to potentially escalate their privileges to SYSTEM level, likely through improper validation in the AppX installation or management process.

MitigationApply the Microsoft security update KB5012345 (or subsequent relevant patches) to affected Windows systems. In enterprise environments, test AppX deployment functionality after patching to ensure no disruption to Windows Store app provisioning.

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= 1909
Windows 11Operating system
Affected:all versions
Windows Server 2016Operating system
Affected:all versions= 20h2
Windows Server 2019Operating system
Affected:all versions
Windows Server 2022Operating 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows version and build number
    Affected if The version matches any of the affected versions listed (Windows 10 1607, 1809, 1909, 20h2, 21h1, 21h2; Windows 11 all versions; Windows Server 2016, 2019, 2022)
  2. Confirm AppX Package Manager component exists
    Verify the presence of AppX deployment cmdlets by running 'Get-Command Appx* -ErrorAction SilentlyContinue' or checking for 'C:\Windows\System32\AppxPackaging.dll'
    Affected if The AppX packaging components are present on the system, which is standard in affected Windows versions
  3. Check AppX deployment capabilities accessible to current user
    Run 'whoami /priv' to list current user privileges, then attempt 'Get-AppxPackage -AllUsers' or check if the user has access to Add-AppxPackage cmdlet
    Affected if A low-privilege authenticated user can access AppX deployment APIs or has limited but exploitable AppX management capabilities
  4. Verify vulnerability is unpatched
    Check installed updates for KB5012345 by running 'Get-HotFix | Where-Object {$_.HotFixID -eq "KB5012345"}' or view installed updates via 'wmic qfe list'
    Affected if The system is missing KB5012345 (or subsequent relevant patches), indicating the security update has not been applied

The system is affected if it runs an affected Windows version (10, 11, Server 2016/2019/2022) with AppX Package Manager components present and lacks the KB5012345 security patch.

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 KB5012345 (or subsequent relevant patches) to affected Windows systems. In enterprise environments, test AppX deployment functionality after patching to ensure no disruption to Windows Store app provisioning.

Recommended fix Moderate confidence
  1. Open Settings on the Windows system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install all available updates
  4. Alternatively, manually download the specific security update from the Microsoft Update Catalog
  5. Ensure KB5010359 (February 2022 security updates) is installed for Windows 10 version 21h2
  6. Ensure KB5010359 is installed for Windows 11
  7. Ensure KB5010359 is installed for Windows Server 2019 and Windows Server 2022
  8. Restart the system after updates are installed

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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