There is a workaround that addresses this vulnerability.
Disable UDP forwarding
UDP forwarding is enabled by default for DNS, TFTP, TACACS, IEN 116 Name Service, NetBIOS Name Service (NBNS), and NetBIOS Datagram Service (NBDS) protocols. UDP forwarding is not enabled by default for other UDP protocols.
If UDP forwarding is not required, a workaround is to disable UDP forwarding globally by using the forward-protocol udp disable command as shown in the following example:
RP/0/RSP0/CPU0:ios#configure terminal
RP/0/RSP0/CPU0:ios(config)#forward-protocol udp disable
RP/0/RSP0/CPU0:ios(config)#commit
Note: If UDP broadcast forwarding is required for any default protocol or if UDP broadcast forwarding has been configured with the forward-protocol udp command, this workaround cannot be used.
While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.