KB ID 0001687
WARNING: This is rated 10 on the CVSS scale.
Affected Server OS: Windows 2003, Windows 2008, Windows 2008 R2, Windows 2012, Windows 2012 R2, Windows 2016, Windows 2019
Yesterday Microsoft released a critical notice (KB4569509) to address vulnerabilities identified in (CVE-2020-1350). Basically it allows a remote attacker to perform remote code execution on your DNS servers (unless you patch them!) The reason its so important is that its considered ‘wormable’, (can jump from machine to machine with our user interaction).
To see how easy that is to do, watch the video below;
To be attacked from an external source the DNS Server has to be publicly addressable, however if you have a compromised machine in your network, it wont be long before a malicious payload can be delivered from that vector also.
The correct fix is to update you servers from Windows Update as soon as possible! However if you want to protect yourself in the interim.
You need to make a slight change in the Windows DNS Server registry. I’ve written the PowerShell out, to save you poking around in the registry, it will change the key for you, and then restart the DNS Service.
# Set DNS Registry Key (Vulnerability CVE-2020-1350) $RegKey ="HKLM:\SYSTEM\CurrentControlSet\Services\DNS\Parameters" Set-ItemProperty -Path $RegKey -Name TcpReceivePacketSize -Value 0xFF00 Get-ItemProperty -Path. -Name TcpReceivePacketSize Restart-Service DNS
If you have a Cisco Firewall you can use the default DNS inspection to mitigate this, RFC 1035 define DNS packets should be less than 512 bytes. But Window uses EDNS so you may have “message-length maximum client auto” in your config, If you remove that, and change the maximum allowed size to 65280 you will mitigate THIS problem. Though I don’t like that as a solution, (unless you have a lot of DNS servers to update, and want to throw in a quick fix while you patch them all).
Note: This vulnerability has existed for 17 years! But now it’s public knowledge, so the clock is ticking before it gets exploited, ACT NOW!
Related Articles, References, Credits, or External Links