Information
If multicast traffic is forwarded beyond the intended boundary, it is possible that it can be intercepted by unauthorized or unintended personnel.
Administrative scoped multicast addresses are locally assigned and are to be used exclusively by the enterprise network or enclave. Administrative scoped multicast traffic must not cross the enclave perimeter in either direction. Restricting multicast traffic makes it more difficult for a malicious user to access sensitive traffic.
Admin-Local scope is encouraged for any multicast traffic within a network intended for network management, as well as for control plane traffic that must reach beyond link-local destinations.
Solution
Step 1: Configure the ACL to deny packets with multicast administratively scoped destination addresses as shown in the example below.
RP/0/0/CPU0:R2(config)#Ipv4 access-list MULTICAST_SCOPE
RP/0/0/CPU0:R2(config-ipv4-acl)#deny 239.0.0.0 0.255.255.255
RP/0/0/CPU0:R2(config-ipv4-acl)#permit any
Step 2: Apply the multicast boundary at the appropriate interfaces as shown in the example below.
RP/0/0/CPU0:R2(config)#multicast-routing
RP/0/0/CPU0:R2(config-mcast)#address-family ipv4
RP/0/0/CPU0:R2(config-mcast-default-ipv4)#int g0/0/0/1
RP/0/0/CPU0:R2(config-mcast-default-ipv4-if)#boundary MULTICAST_SCOPE
RP/0/0/CPU0:R2(config-mcast-default-ipv4-if)#end