A vulnerability was found in BIRD Internet Routing Daemon 1.6.x through 1.6.7 and 2.x through 2.0.5 has a stack-based buffer overflow. The BGP daemon's support for RFC 8203 administrative shutdown communication messages included an incorrect logical expression when checking the validity of an input message. Sending a shutdown communication with a sufficient message length causes a four-byte overflow to occur while processing the message, where two of the overflow bytes are attacker-controlled and two are fixed. Reference: http://trubka.network.cz/pipermail/bird-users/2019-September/013718.html http://trubka.network.cz/pipermail/bird-users/2019-September/013720.html http://trubka.network.cz/pipermail/bird-users/2019-September/013722.html https://gitlab.labs.nic.cz/labs/bird/commit/1657c41c96b3c07d9265b07dd4912033ead4124b https://gitlab.labs.nic.cz/labs/bird/commit/8388f5a7e14108a1458fea35bfbb5a453e2c563c
Created bird tracking bugs for this issue: Affects: epel-all [bug 1751033] Affects: fedora-all [bug 1751032] Created bird2 tracking bugs for this issue: Affects: epel-all [bug 1751034]
External References: https://bird.network.cz/
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.
Note that it is *not* true that this is fixed in versions 2.0.5 and 1.6.7. The fixes are in upstream git, but not yet in a released version. See http://trubka.network.cz/pipermail/bird-users/2019-September/013722.html - specifically: The bugfix patches are: 1657c41c96b3c07d9265b07dd4912033ead4124b (1.6.x) 8388f5a7e14108a1458fea35bfbb5a453e2c563c (2.0.x) I'm clearing the "fixed in upstream" field, but not sure if the bug should also be reopened?