Skip to main content
Mallory
HighVulnerability

CVE-2019-0630: SMBv2 Remote Code Execution Vulnerability (CVE-2019-0630)

Published Mar 6, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3
EPSS17.4%97th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2019-0630CWE-787

CVE-2019-0630 is a remote code execution vulnerability in the Microsoft Server Message Block 2.0 (SMBv2) server. The vulnerability exists due to improper handling of certain requests by the SMBv2 server, which could allow an authenticated attacker to execute arbitrary code on the target system. This vulnerability is distinct from CVE-2019-0633 and affects Windows systems with SMBv2 enabled.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of this vulnerability allows an authenticated attacker to execute arbitrary code on the affected system, potentially leading to full system compromise. The attacker must have valid credentials to exploit the vulnerability, limiting the attack vector to authenticated users. However, remote code execution in SMB can facilitate lateral movement and further compromise within a network.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, consider disabling SMBv2 where feasible, or restrict access to SMB services to trusted hosts only. Network segmentation and firewall rules can also be used to limit exposure of SMB services to untrusted networks. Monitor for unusual SMB activity and enforce strong authentication policies.

Remediation

Patch, then assume compromise.

Apply the security updates released by Microsoft in February 2019 for all affected Windows systems. These updates address the vulnerability by correcting the way SMBv2 handles certain requests. Ensure all systems are patched promptly to mitigate the risk of exploitation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
FAQ

Frequently asked questions

Is CVE-2019-0630 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2019-0630 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-0630?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2019-0630.
Is there a patch for CVE-2019-0630?
Apply the security updates released by Microsoft in February 2019 for all affected Windows systems. These updates address the vulnerability by correcting the way SMBv2 handles certain requests.
What products are affected by CVE-2019-0630?
Microsoft Corporation Windows 10, Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Rt 8.1, Microsoft Corporation Windows Server 2008, and 3 more.
How severe is CVE-2019-0630?
CVE-2019-0630 has a CVSS v3 score of 8.8 (High) and an EPSS score of 17.4% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.