CVE-2023-41358

7.5 HIGH

📋 TL;DR

A NULL pointer dereference vulnerability in FRRouting's BGP daemon allows remote attackers to cause denial of service by sending specially crafted BGP packets with zero-length attributes. This affects FRRouting installations running BGP, potentially disrupting network routing.

💻 Affected Systems

Products:
  • FRRouting (FRR)
Versions: All versions through 9.0
Operating Systems: Linux distributions including Debian, Fedora, Ubuntu
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with BGP enabled and configured

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete BGP daemon crash leading to routing table loss and network connectivity disruption

🟠

Likely Case

BGP daemon crash requiring manual restart, causing temporary routing instability

🟢

If Mitigated

Minimal impact if proper segmentation and monitoring are in place

🌐 Internet-Facing: HIGH - BGP peers are typically internet-facing and can be targeted by remote attackers
🏢 Internal Only: MEDIUM - Internal BGP peers could exploit but require network access

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW - Requires sending malformed BGP packets

Exploitation requires BGP peer relationship or ability to send BGP packets to vulnerable system

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Fixed in FRR 9.0.1 and later

Vendor Advisory: https://github.com/FRRouting/frr/pull/14260

Restart Required: Yes

Instructions:

1. Update FRR to version 9.0.1 or later. 2. For Debian/Fedora: Use package manager updates. 3. Restart bgpd service: 'systemctl restart frr' or 'service frr restart'

🔧 Temporary Workarounds

BGP Peer Filtering

linux

Restrict BGP peer connections to trusted sources only

# Configure BGP peer filtering in frr.conf
neighbor <trusted-peer> remote-as <as-number>
neighbor <trusted-peer> prefix-list trusted-peers in

🧯 If You Can't Patch

  • Implement strict BGP peer authentication using MD5 or TCP-AO
  • Deploy network segmentation to isolate BGP traffic from untrusted networks

🔍 How to Verify

Check if Vulnerable:

Check FRR version: 'frr --version' or 'vtysh -c 'show version''. If version is 9.0 or earlier, system is vulnerable.

Check Version:

frr --version

Verify Fix Applied:

Verify FRR version is 9.0.1 or later. Check bgpd process is running: 'systemctl status frr' or 'ps aux | grep bgpd'

📡 Detection & Monitoring

Log Indicators:

  • BGP daemon crashes in syslog
  • Unexpected bgpd restarts
  • BGP session resets with malformed packet errors

Network Indicators:

  • BGP UPDATE packets with zero-length attributes
  • Unexpected BGP session terminations

SIEM Query:

source="syslog" AND ("bgpd" OR "frr") AND ("crash" OR "segfault" OR "restart")

🔗 References

📤 Share & Export