RIPd in Quagga accepts RIPv1 RESPONSE when RIPv2 authentication is
enabled. This condition is possible unless RIPv2 only is specified in
the RIPd configuration. This flaw could allow a remote attacker to
inject a route via RIPv1 RESPONSE packets.
This issue also affects zebra.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.