3 ms·
Here is the registry work around for those that can not patch right now. [0] To work around this vulnerability, make the following registry change to restrict
by LinuxBender 6y ago
Here is the registry work around for those that can not patch right now. [0]
To work around this vulnerability, make the following registry change to restrict the size of the largest inbound TCP-based DNS response packet that's allowed:
Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
Value: TcpReceivePacketSize
Type: DWORD
Value data: 0xFF00
The default (also maximum) Value data = 0xFFFF.
The recommended Value data = 0xFF00 (255 bytes less than the maximum).
You must restart the DNS Service for the registry change to take effect. To do this, run the following command at an elevated command prompt:
net stop dns && net start dns
[0] - https://support.microsoft.com/en-us/help/4569509/windows-dns-server-remote-code-execution-vulnerability https://support.microsoft.com/en-us/help/4569509/windows-dns...