Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Took from upstream report
"Hi,
I noticed a little security issue in the pimd processing of IGMP Queries. It appears to me that, upon reception of an IGMP General Query, no check is done on the destination address.
However in RFC3376, which specifies IGMPv3, is stated this :
4.1.12. IP Destination Addresses for Queries
In IGMPv3, General Queries are sent with an IP destination address of 224.0.0.1, the all-systems multicast address.
If not check is made upon reception of an IGMPv3 General Query, this query can be received on the unicast IPv4 address of the router as if it was sent to the All-Systems multicast address (which makes no difference to the router, but makes some for all the other systems on the local network link).
From there, an attacker can send General Queries to the router periodically with a lower IP source address, putting it in a Non-Querier State.
In this state, there are no general queries sent to the segment and the multicast states kept by the router will eventually time out, provoking a denial of service on the multicast service."
https://github.com/FRRouting/frr/issues/1692
Additional info:
upstream commit addressing this issue:
https://github.com/donaldsharp/frr/commit/ff4516227cc48b3175106a419f43b8fc9eee3710
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: frr security and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4619
Description of problem: Took from upstream report "Hi, I noticed a little security issue in the pimd processing of IGMP Queries. It appears to me that, upon reception of an IGMP General Query, no check is done on the destination address. However in RFC3376, which specifies IGMPv3, is stated this : 4.1.12. IP Destination Addresses for Queries In IGMPv3, General Queries are sent with an IP destination address of 224.0.0.1, the all-systems multicast address. If not check is made upon reception of an IGMPv3 General Query, this query can be received on the unicast IPv4 address of the router as if it was sent to the All-Systems multicast address (which makes no difference to the router, but makes some for all the other systems on the local network link). From there, an attacker can send General Queries to the router periodically with a lower IP source address, putting it in a Non-Querier State. In this state, there are no general queries sent to the segment and the multicast states kept by the router will eventually time out, provoking a denial of service on the multicast service." https://github.com/FRRouting/frr/issues/1692 Additional info: upstream commit addressing this issue: https://github.com/donaldsharp/frr/commit/ff4516227cc48b3175106a419f43b8fc9eee3710