CVE-2019-0630: Critical severity windows 10 vulnerability

Published Mar 5, 2019

Updated

A remote code execution vulnerability exists in the way that the Microsoft Server Message Block 2.0 (SMBv2) server handles certain requests, aka 'Windows SMB Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0633.

Affected Software

19 affected components

Microsoft Windows 10

Microsoft Windows 10=1607

Microsoft Windows 10=1703

Microsoft Windows 10=1709

Microsoft Windows 10=1803

Microsoft Windows 10=1809

Microsoft Windows 7=sp1

Microsoft Windows 8.1

Microsoft Windows RT 8.1

Microsoft Windows Server 2008=sp2

Microsoft Windows Server 2008=r2-sp1

Microsoft Windows Server 2012

Microsoft Windows Server 2012=r2

Microsoft Windows Server 2016

Microsoft Windows Server 2016=1709

Microsoft Windows Server 2016=1803

Microsoft Windows Server 2019

Remediation

Patch Available

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0630

Event History

Mar 5, 2019

CVE Published

11:29 PM

Mar 6, 2019

CVE Published

via MITRE·12:00 AM

Data Sourced

via MITRE·12:00 AM

DescriptionWeakness

Frequently Asked Questions

What is the severity of CVE-2019-0630?

CVE-2019-0630 has a critical severity rating due to its potential for remote code execution.

How do I fix CVE-2019-0630?

To fix CVE-2019-0630, you should apply the relevant security updates provided by Microsoft.

What software is affected by CVE-2019-0630?

CVE-2019-0630 affects various versions of Microsoft Windows including Windows 10, Windows 7, Windows 8.1, and Windows Server editions.

Can CVE-2019-0630 be exploited remotely?

Yes, CVE-2019-0630 allows attackers to execute arbitrary code remotely, making it highly exploitable.

Is there a workaround for CVE-2019-0630?

While applying updates is recommended, disabling SMBv2 may serve as a temporary workaround for CVE-2019-0630.