dbcve.org
Windows 10Operating system · Microsoft

CVE-2019-0719

CRITICAL · 9.1 CVSS v3.1 Published 2019-11-12
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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
A remote code execution vulnerability exists when Windows Hyper-V Network Switch on a host server fails to properly validate input from an authenticated user on a guest operating system, aka 'Hyper-V Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0721.

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
How this class of weakness works · CWE-20

The application accepts input without confirming it is well-formed or within expected bounds, so malformed data can push the program into states its author never anticipated. Attackers probe these gaps to trigger crashes, bypass logic, or feed tainted values into more dangerous operations downstream. Remediating it well means validating and normalising every input at the boundary against a strict allow-list — not merely filtering known-bad values.

General guidance for the improper input validation class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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= 1607= 1709= 1803= 1809= 1903
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions= 1803= 1903
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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

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
Vendor patch portal.msrc.microsoft.com →
Recommended fix High confidence

For end-of-life systems (Windows 7, Server 2008, Server 2012): Upgrade to Windows 10 1909+ or Windows Server 2019/2022. For in-support systems: Apply the August 2019 or later Windows cumulative security update.

  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows 10: Open Settings > Update & Security > Windows Update and check for updates, or manually download the applicable security update from the Microsoft Update Catalog for your specific build (1607, 1709, 1803, or later)
  3. For Windows 8.1, Server 2012, Server 2012 R2, Server 2016, Server 2019: Use Windows Update or download the relevant security update from the Microsoft Update Catalog
  4. For Windows 7 and Windows Server 2008 R2: These versions are end-of-life; Microsoft issued the final patches in January 2020 - obtain the relevant patch from Windows Update if not already applied, otherwise upgrade to a supported OS
  5. After installing the update, restart the Hyper-V host server to apply the changes
  6. Verify the update was installed successfully by checking Windows Update history for the CVE-2019-0719 security update
Caveat Windows 7 and Server 2008 R2 reached end of support in January 2020 - no further security patches are available; migrating to a supported OS version is required. Ensure guest VMs are backed up before patching the Hyper-V host.

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

We can apply and verify the patch for your build — typical engagement from $2,300. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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