CVE-2023-41361

Public on

Last Modified: UTC

Description

A vulnerability was found in FRRouting stemming from a boundary error in bgpd/bgp_open.c. The issue arises because it fails to check for an excessively large length of the received software version (rcv). This flaw allows a remote attacker to overflow a buffer by sending specially crafted data to the application, leading to a denial of service condition.

A vulnerability was found in FRRouting stemming from a boundary error in bgpd/bgp_open.c. The issue arises because it fails to check for an excessively large length of the received software version (rcv). This flaw allows a remote attacker to overflow a buffer by sending specially crafted data to the application, leading to a denial of service condition.

Statement

In Red Hat Enterprise Linux 8 and 9, the vulnerable code is not included. It was added much later during the development of the 9.x version of FRR in upstream. The highest version of FRR utilized in RHEL is 8.5. Consequently, none of the FRR versions shipped in RHEL are affected by this vulnerability.

In Red Hat Enterprise Linux 8 and 9, the vulnerable code is not included. It was added much later during the development of the 9.x version of FRR in upstream. The highest version of FRR utilized in RHEL is 8.5. Consequently, none of the FRR versions shipped in RHEL are affected by this vulnerability.

Additional information

  • Bugzilla 2235844: frr: does not check for an overly large length of the rcv software version
  • CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
  • FAQ: Frequently asked questions about CVE-2023-41361

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown
Red HatNVD

CVSS v3 Base Score

5.9

9.8

Attack Vector

Network

Network

Attack Complexity

High

Low

Privileges Required

None

None

User Interaction

None

None

Scope

Unchanged

Unchanged

Confidentiality Impact

None

High

Integrity Impact

None

High

Availability Impact

High

High

CVSS v3 Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

NVD: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Red Hat CVSS v3 Score Explanation

AC:H, as exploiting this is difficult to do and heavily depends on the application you're targeting. C:N, I:N, Reading and writing data typically doesn't pose a direct or significant threat, as the FRR packages included in Red Hat Enterprise Linux (RHEL) are compiled with certain stack and heap protections enabled. These measures help mitigate the overall impact, making it more probable that any potential consequences would result in a Denial of Service (DoS) rather than more severe issues.

AC:H, as exploiting this is difficult to do and heavily depends on the application you're targeting.

C:N, I:N, Reading and writing data typically doesn't pose a direct or significant threat, as the FRR packages included in Red Hat Enterprise Linux (RHEL) are compiled with certain stack and heap protections enabled. These measures help mitigate the overall impact, making it more probable that any potential consequences would result in a Denial of Service (DoS) rather than more severe issues.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.