etc. (predictable IP fragmentation ID) in "regular" IP
packets and raw IP packets.
o Predictable IP fragmentation ID in Ethernet-inside-IP
encapsulation, IP-inside-IP encapsulation, the CARP
protocol, IP multicast routing, pfsync interface
protocol, packet filter (IP packet normalization), and
network bridge (ICMP error packets).
* OpenBSD 2.5-4.2
> etc. (predictable IP fragmentation ID) in "regular" IP
> packets and raw IP packets.
>
> o Predictable IP fragmentation ID in Ethernet-inside-IP
> encapsulation, IP-inside-IP encapsulation, the CARP
> protocol, IP multicast routing, pfsync interface
> protocol, packet filter (IP packet normalization), and
> network bridge (ICMP error packets).
>
>
> * OpenBSD 2.5-4.2
Note that available PIM modes on a Cisco IOS device are dense mode,
sparse mode, or sparse-dense mode. A device that is configured for
any of these modes is affected by these vulnerabilities. The mode
determines how the device populates its multicast routing table and
how multicast packets are forwarded. PIM must be enabled in one of
these modes for an interface to perform IP multicast routing. More
information on the configuration of each mode is in the "Details"
section.
Additionally, To display information about interfaces configured for
Protocol Independent Multicast (PIM), use the show ip pim interface
=======
MVPN architecture introduces an additional set of protocols and
procedures that help enable a service provider to support multicast
traffic in an MPLS VPN. MVPN allows the transparent transport of IP
multicast traffic across the MPLS VPN backbone of a provider and
allows a service provider to offer multicast services to MPLS VPN
customers.
A vulnerability exists in the implementation of MVPN that allows an
attacker to send specially crafted Multicast Distribution Tree (MDT)
