SMBv3 compression on a Windows build affected by SMBGhost
| Finding id | cve-cve-2020-0796 |
| Severity | High |
| Applies to | TCP port 445 (SMB), scans with Safe Mode off |
What it means
The server uses SMB 3.1.1 with compression on a Windows 10 or Windows Server build (version 1903 or 1909) that was affected by SMBGhost (CVE-2020-0796), a flaw that allowed remote code execution through a crafted compressed SMB message. Microsoft fixed it in March 2020.
Why it matters
On an unpatched system the flaw can be exploited over the network without logging in. The finding is a hint to check the patch level, because the scan cannot see it.
How it is detected
The finding requires all of these: the SMB2 negotiate reply selects dialect 3.1.1; it announces a compression algorithm; and the NTLM challenge identifies the Windows build as 10.0.18362 or 10.0.18363 (Windows 10 or Server 1903/1909). The NTLM challenge is only requested when Safe Mode is off (a session setup message without credentials is sent), so in Safe Mode this finding is never raised. The evidence names the dialect, the compression and the build.
This rule is built into the program, separately from the version rules in cves.json. The patch level (KB4551762) is not visible to a remote scan, so patched and unpatched systems look the same.
Possible false positives
- Hosts that have installed the March 2020 update or later still show the same dialect, compression and build, and are reported. Treat the finding as “check the patch level”, not as proof of vulnerability.
How to fix
- Install the Microsoft update KB4551762 (March 2020) or any later cumulative update.
- Workaround from Microsoft’s advisory: disable SMBv3 compression on the server:
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" DisableCompression -Type DWORD -Value 1 -Force; no restart is required. - Windows 10 1903 and 1909 are out of support: upgrade to a supported release.
- Block TCP 445 at the network edge and between segments where file sharing is not needed.
- Industrial and embedded devices (OT): settings like this can often only be changed with the vendor’s tools or a firmware update. Follow the vendor’s guidance, try the change on a spare unit first, and apply it in an agreed change window with the plant operators informed; a changed setting can interrupt communication with a running process.
- The finding goes away when the Windows build is no longer 1903/1909 or SMB compression is off. Installing the update alone does not change what a scan sees, so record the patch level separately.