CVE-2019-1322
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 Windows improperly handles authentication requests, aka 'Microsoft Windows Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2019-1320, CVE-2019-1340.
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 confidenceA local elevation of privilege vulnerability in Microsoft Windows where the operating system improperly handles authentication requests, allowing an authenticated attacker to gain higher privileges on the system.
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 version and buildRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' from command prompt to obtain the installed Windows version and build numberAffected if The version shown is Windows 10 1803, 1809, or 1903, or Windows Server 1803, 1903, or 2019
-
Confirm authentication feature is in useVerify the system accepts authentication requests (domain-joined or local user accounts are active). This is typically the default state for Windows systems.Affected if The system has user authentication enabled, which is the standard configuration for affected Windows installations
-
Check if security update is appliedOpen Control Panel > Programs > View installed updates, or run 'wmic qfe list' to see installed hotfixes. Look for the security update addressing CVE-2019-1322.Affected if No security update for CVE-2019-1322 appears in the installed updates list, meaning the system remains vulnerable
A system is affected if it runs Windows 10 1803/1809/1903 or Windows Server 1803/1903/2019 and lacks the specific security update for CVE-2019-1322.
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 update for this vulnerability (KB4512574 or subsequent patches) to all affected Windows systems.
Windows 10 1803/1809/1903 -> Windows 10 21H2 or later (or Windows 11); Windows Server 1803/1903/2019 -> Windows Server 2022 or later
- Verify current Windows version by running 'winver' command
- Open Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest cumulative security update
- Alternatively, manually download the security update for this CVE from the Microsoft Update Catalog
- Restart the computer when prompted to complete the installation
- Confirm the security update is installed by checking Windows Update history
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1322 — 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-1322 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