CVE-2024-31950 is a buffer overflow vulnerability identified in FRRouting (FRR) software versions through 9.1, specifically within the ospf_te_parse_ri function that handles OSPF Traffic Engineering (TE) Link State Advertisements (LSAs). The vulnerability arises because the code attempts to read Segment Routing sub-Type-Length-Value (subTLV) structures without properly validating their size, leading to a buffer overflow condition. This improper bounds checking can cause the FRR daemon to crash, resulting in a denial of service. The vulnerability is exploitable remotely over the network without requiring any authentication or user interaction, as OSPF LSA packets are exchanged between routers. The CVSS v3.1 base score is 6.5 (medium severity), reflecting the network attack vector, low attack complexity, no privileges required, and no user interaction needed, with limited impact on confidentiality and integrity but no impact on availability. No patches or known exploits have been reported at the time of disclosure. The underlying weakness corresponds to CWE-120 (Classic Buffer Overflow). Since FRRouting is widely used in network routing infrastructure, especially in environments leveraging OSPF with Segment Routing extensions, this vulnerability poses a risk to the stability and reliability of routing daemons and potentially the broader network.

The primary impact of CVE-2024-31950 is denial of service through daemon crashes in FRRouting, which can disrupt OSPF routing operations and network stability. This can lead to routing outages, degraded network performance, and potential traffic loss or misrouting. Although the CVSS score indicates limited confidentiality and integrity impact, memory corruption from buffer overflows can sometimes be leveraged for more advanced exploits, though no such exploits are currently known. Organizations relying on FRRouting for OSPF with Segment Routing extensions, particularly in large-scale or critical network environments such as ISPs, data centers, and enterprise WANs, face increased operational risk. Network availability and reliability could be compromised, affecting business continuity and service delivery. The vulnerability's remote exploitability without authentication increases the attack surface, especially in environments where OSPF packets are exchanged over untrusted or semi-trusted networks.

To mitigate CVE-2024-31950, organizations should monitor FRRouting project updates and apply patches promptly once available. In the absence of an official patch, network administrators can implement the following practical measures: 1) Restrict OSPF traffic to trusted network segments using access control lists (ACLs) or firewall rules to limit exposure to potentially malicious OSPF LSA packets. 2) Employ network segmentation to isolate routing protocol traffic from untrusted networks. 3) Monitor FRRouting daemon logs and network traffic for abnormal OSPF LSA packets or daemon crashes indicative of exploitation attempts. 4) Consider disabling Segment Routing extensions in OSPF if not required, reducing the attack surface. 5) Use intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics to detect malformed OSPF packets. 6) Maintain up-to-date backups and recovery procedures to quickly restore routing functionality if disruption occurs. These steps go beyond generic advice by focusing on protocol-specific controls and operational monitoring tailored to FRRouting and OSPF environments.