Skip to content
Fencer Vulns
critical 9.1

CVE-2023-41359 json

An issue was discovered in FRRouting FRR through 9.0.

published 2023-08-29 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-45862

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

Summary

An issue was discovered in FRRouting FRR through 9.0. There is an out-of-bounds read in bgp_attr_aigp_valid in bgpd/bgp_attr.c because there is no check for the availability of two bytes during AIGP validation.

Patch / fix

  • frr RHEL 9 8.5.3-4.el9
  • frr-selinux RHEL 9 8.5.3-4.el9

red hat advisories RHSA-2024:2156

  • frr AlmaLinux 9 8.5.3-4.el9
  • frr-selinux AlmaLinux 9 8.5.3-4.el9

almalinux advisories ALSA-2024:2156

  • frr CBL-Mariner 2.0 8.5.3-2

azure linux advisories AZL-28615

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

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-2023-41359 updated cvss 5.9

frr: out of bounds read in bgp_attr_aigp_valid

  • Red Hat Enterprise Linux AppStream (v. 9) frr 8.5.3-4.el9, frr-selinux 8.5.3-4.el9
    fixed: vendor fix RHSA-2024:2156
  • 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

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

CVSS scores

assigned by version score vector
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.