Skip to main content
CVE-2024-44070VulnerabilityPublished Updated

CVE-2024-44070: frr · n/a

Affects frrSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubfrrouting/frrpkg:github/frrouting/frrOther threatsAffected
  • <=10.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor FRRouting project channels closely for official patches addressing CVE-2024-44070 and apply them immediately upon release. 2. Implement strict ingress and egress filtering of BGP traffic at network borders to block malformed or suspicious BGP update messages, particularly those containing encapsulation attributes. 3. Employ BGP session authentication mechanisms such as TCP MD5 signatures or TCP-AO to reduce the risk of unauthorized BGP message injection. 4. Use network anomaly detection systems to identify unusual BGP update patterns or traffic spikes indicative of exploitation attempts. 5. Segment routing infrastructure from general-purpose networks to limit exposure. 6. Regularly audit and update routing software versions to minimize exposure to known vulnerabilities. 7. Coordinate with upstream providers and peers to ensure consistent security postures and rapid incident response capabilities.

Description

An issue was discovered in FRRouting (FRR) through 10.1.bgp_attr_encap in bgpd/bgp_attr.c does not check the actual remaining stream length before taking the TLV value.

References

Community reviews

Loading reviews…