A critical vulnerability in FRRouting versions 2.0 through 10.4.1 allows remote, unauthenticated attackers to crash the service and cause a denial of service.

The flaw is a NULL pointer dereference occurring within the opaque_info_detail function of the ospf_opaque.c source file. This vulnerability is remotely exploitable by an unauthenticated attacker who sends a specifically crafted Link State (LS) Update packet to the target system.

Successful exploitation of this vulnerability results in a Denial of Service (DoS) condition, which can render routing protocols unresponsive and disrupt network traffic flow. Given the CVSS score of 7.5, this high-severity flaw poses a significant risk to network availability and infrastructure stability. Organizations relying on FRRouting for critical routing services face potential operational downtime if this vulnerability is triggered.

Immediate Action: Review the FRRouting project repository and apply the upstream fix associated with commit 88f5c06cbc1cc4d62e1cba3e7791f5cea4179ba5 once integrated into your distribution.

Proactive Monitoring: Monitor system logs for repeated OSPF process crashes or unexpected service restarts that may indicate attempted exploitation of this NULL pointer flaw.

Compensating Controls: Implement Access Control Lists (ACLs) to restrict OSPF packet intake to trusted peers only, effectively limiting the attack surface for this unauthenticated vector.

Public Exploit Available: Yes — a published proof-of-concept exists as documented in the researcher write-up linked in the references.

This vulnerability presents a clear risk to network reliability due to the ease with which a DoS can be triggered. Administrators should prioritize applying the vendor-provided patch or updating to a version beyond 10.4.1 as soon as it becomes available to prevent potential service interruptions.