Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 13 Jun 2022. Known ransomware use
Windows 10 1709Operating system · Microsoft

CVE-2019-1385

HIGH · 7.8 CVSS v3.1 Published 2019-11-12
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
In the wild Ransomware Zero-click Patch available

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
An elevation of privilege vulnerability exists when the Windows AppX Deployment Extensions improperly performs privilege management, resulting in access to system files.To exploit this vulnerability, an authenticated attacker would need to run a specially crafted application to elevate privileges.The security update addresses the vulnerability by correcting how AppX Deployment Extensions manages privileges., aka 'Windows AppX Deployment Extensions 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

An elevation of privilege vulnerability in Windows AppX Deployment Extensions allows an authenticated attacker to run a specially crafted application that gains unauthorized access to system files due to improper privilege management during app deployment operations.

MitigationApply the Microsoft security update that corrects privilege management in the AppX Deployment Extensions component. This is a standard Windows OS security patch that should be deployed via organizational patch management processes.

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 10 1709Operating system
Affected:all versions
Windows 10 1803Operating system
Affected:all versions
Windows 10 1809Operating system
Affected:all versions
Windows 10 1903Operating system
Affected:all versions
Windows Server 2016Operating system
Affected:all versions
Windows Server 2019Operating 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
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number
    Affected if The displayed version matches Windows 10 1709, 1803, 1809, 1903, Windows Server 2016, or Windows Server 2019 (any build within those releases)
  2. Confirm AppX Deployment capability
    Verify that AppX deployment extensions are available by checking for the presence of 'AppxPackaging.dll' in C:\Windows\System32 or by running 'Get-AppxPackage' in PowerShell to list installed AppX packages
    Affected if The system returns AppX package listings or the DLL exists, indicating AppX deployment functionality is present
  3. Check for security update
    Open Control Panel > Programs > Programs and Features > View installed updates, or run 'wmic qfe list' in Command Prompt to display installed hotfixes
    Affected if No security update specifically addressing AppX Deployment Extensions privilege management is installed for this CVE

You are affected if your Windows version matches Windows 10 1709, 1803, 1809, 1903, Windows Server 2016, or Windows Server 2019 AND the corresponding security update for CVE-2019-1385 is not installed.

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
Patch available Apply the vendor patch
Interim mitigation

Apply the Microsoft security update that corrects privilege management in the AppX Deployment Extensions component. This is a standard Windows OS security patch that should be deployed via organizational patch management processes.

Recommended fix High confidence

Windows 10 1909 or later, or Windows 11 (for desktop); Windows Server 2019 with latest cumulative update (for server)

  1. 1. Identify the current Windows version by opening Settings > System > About
  2. 2. Determine if your current version is still within its support lifecycle at https://docs.microsoft.com/en-us/lifecycle/
  3. 3. If on Windows 10 1709, 1803, 1809, or 1903, upgrade to a supported Windows 10 version (1909 or later) or Windows 11
  4. 4. If on Windows Server 2016 or 2019, ensure you apply the latest cumulative security updates from Windows Update
  5. 5. Run Windows Update and install all pending security updates, specifically the patch for CVE-2019-1385
  6. 6. After updating, verify the vulnerability is patched by checking that the AppX Deployment Service operates with proper privilege constraints
Caveat Upgrading Windows versions may require application compatibility testing; ensure backups and rollback plans are in place before proceeding

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

Fix this in Windows 10 1709 Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1385 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1385 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