CVE-2019-1385
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 · uneditedAn 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 confidenceAn 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.
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 versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows versionOpen Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build numberAffected if The displayed version matches Windows 10 1709, 1803, 1809, 1903, Windows Server 2016, or Windows Server 2019 (any build within those releases)
-
Confirm AppX Deployment capabilityVerify 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 packagesAffected if The system returns AppX package listings or the DLL exists, indicating AppX deployment functionality is present
-
Check for security updateOpen Control Panel > Programs > Programs and Features > View installed updates, or run 'wmic qfe list' in Command Prompt to display installed hotfixesAffected 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.
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 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.
Windows 10 1909 or later, or Windows 11 (for desktop); Windows Server 2019 with latest cumulative update (for server)
- 1. Identify the current Windows version by opening Settings > System > About
- 2. Determine if your current version is still within its support lifecycle at https://docs.microsoft.com/en-us/lifecycle/
- 3. If on Windows 10 1709, 1803, 1809, or 1903, upgrade to a supported Windows 10 version (1909 or later) or Windows 11
- 4. If on Windows Server 2016 or 2019, ensure you apply the latest cumulative security updates from Windows Update
- 5. Run Windows Update and install all pending security updates, specifically the patch for CVE-2019-1385
- 6. After updating, verify the vulnerability is patched by checking that the AppX Deployment Service operates with proper privilege constraints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1385 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