CVE-2020-12831
LowSummary
In FRRouting (FRR) up to version 7.3.1, when using the split-config feature, the init script creates an empty config file with world-readable default permissions, potentially leading to information leakage via frr.in and frrcommon.sh.in tools.
Risk Assessment
The risk involves potential disclosure of sensitive network configuration data to unauthorized local users, which could facilitate attacks on routing infrastructure.
Recommendation
It is recommended to upgrade FRRouting to a version newer than 7.3.1 and manually set appropriate permissions (e.g., 600) for configuration files created by the init script.
Other vulnerabilities in FRRouting
See all- CVE-2026-37460High
Missing input validation in the rfapiRibBi2Ri() function (rfapi_rib.c) in FRRouting (FRR) from stable/10.0 to stable/10.6 allows attackers to cause a Denial of Service (DoS) by supplying a crafted BGP UPDATE message.
- CVE-2026-37459High
An integer underflow vulnerability exists in FRRouting (FRR) versions stable/10.0 through stable/10.6. Attackers can cause a Denial of Service (DoS) by sending a crafted BGP UPDATE message.
- CVE-2026-37457High
An off-by-one out-of-bounds write vulnerability in the bgp_flowspec_op_decode() function of FRRouting (FRR) stable/10.0 allows attackers to cause a Denial of Service (DoS) via a crafted FlowSpec component.
- CVE-2023-3748Low
A flaw was found in FRRouting when parsing certain babeld unicast hello messages that are intended to be ignored. This issue may allow an attacker to send specially crafted hello messages, leading to an infinite loop and causing a denial of service.
Original NVD description (English source)
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 pa
Vulnerability data from NVD (NIST) · CISA KEV · EPSS