An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readable default permissions, leading to a possible information leak via tools/frr.in and tools/frrcommon.sh.in. NOTE: some parties consider this user error, not a vulnerability, because the permissions are under the control of the user before any sensitive information is present in the file
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alma_linux | — | Upgrade frr-contrib | May 4, 2022 | May 13, 2020 |
| Centos_linux | — | Upgrade frr-debuginfoUpgrade frr-debugsourceUpgrade frrUpgrade frr-contrib | Nov 5, 2020 | May 13, 2020 |
| Debian | — | No solution exists | May 15, 2025 | May 13, 2020 |
| Oracle_linux | — | Upgrade frr-contribUpgrade frr | Nov 12, 2020 | May 3, 2020 |
| Redhat_linux | — | Upgrade frr-contribUpgrade frr-debuginfoUpgrade frr-debugsourceUpgrade frr | Nov 5, 2020 | May 13, 2020 |
| Suse | — | Upgrade libfrrospfapiclient0Upgrade libfrrsnmp0Upgrade libfrrgrpc_pb0Upgrade libfrrfpm_pb0Upgrade libfrr0Upgrade libmlag_pb0Upgrade frr-develUpgrade frrUpgrade libfrr_pb0Upgrade libfrrzmq0Upgrade libfrrcares0 | Feb 4, 2022 | May 13, 2020 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub