Remote Procedure Call Runtime Remote Code Execution Vulnerability

How could an attacker exploit this vulnerability?
To exploit this vulnerability, an unauthenticated attacker would need to send a specially crafted RPC call to an RPC host. This could result in remote code execution on the server side with the same permissions as the RPC service.

Is blocking RPC with a perimeter firewall recommended?
Blocking TCP port 135 at the enterprise perimeter firewall is a recommended best practice that could reduce the likelihood of some potential attacks against this vulnerability.

Security updates
10.0.17763.4131 — https://support.microsoft.com/help/5023702
10.0.20348.1607 — https://support.microsoft.com/help/5023705
10.0.20348.1602 — https://support.microsoft.com/help/5023786
10.0.19042.2728 — https://support.microsoft.com/help/5023696
10.0.22000.1696 — https://support.microsoft.com/help/5023698
10.0.22621.1413 — https://support.microsoft.com/help/5023706
10.0.10240.19805 — https://support.microsoft.com/help/5023713
10.0.14393.5786 — https://support.microsoft.com/help/5023697
6.0.6003.21966 — https://support.microsoft.com/help/5023755
6.0.6003.21966 — https://support.microsoft.com/help/5023754
6.1.7601.26415 — https://support.microsoft.com/help/5023769
6.1.7601.26415 — https://support.microsoft.com/help/5023759
6.2.9200.24168 — https://support.microsoft.com/help/5023756
6.2.9200.24168 — https://support.microsoft.com/help/5023752
6.3.9600.20865 — https://support.microsoft.com/help/5023765
6.3.9600.20865 — https://support.microsoft.com/help/5023764