Skip to content
Fencer Vulns
medium 6.5

CVE-2022-43681 json

An out-of-bounds read exists in the BGP daemon of FRRouting FRR through 8.4.

published 2023-05-03 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-46674

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

An out-of-bounds read exists in the BGP daemon of FRRouting FRR through 8.4. When sending a malformed BGP OPEN message that ends with the option length octet (or the option length word, in case of an extended OPEN message), the FRR code reads of out of the bounds of the packet, throwing a SIGABRT signal and exiting. This results in a bgpd daemon restart, causing a Denial-of-Service condition.

Patch / fix

  • frr Debian 14, Debian 13, Debian 12 8.4.1-1

debian advisories DEBIAN-CVE-2022-43681

  • frr RHEL 9 8.3.1-11.el9_3
  • frr-selinux RHEL 9 8.3.1-11.el9_3

red hat advisories RHSA-2023:6434

  • frr AlmaLinux 9 8.3.1-11.el9_3.alma.1
  • frr-selinux AlmaLinux 9 8.3.1-11.el9_3.alma.1

almalinux advisories ALSA-2023:6434

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-43681 updated cvss 6.5

frr: out-of-bounds read exists in the BGP daemon of FRRouting

  • Red Hat Enterprise Linux AppStream (v. 9) frr 8.3.1-11.el9_3, frr-selinux 8.3.1-11.el9_3
    fixed: vendor fix RHSA-2023:6434
  • Red Hat Enterprise Linux 8 frr, frr-contrib, frr-selinux
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.13% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.