CVE-2023-41361

An issue was discovered in FRRouting FRR 9.0. bgpd/bgp_open.c does not check for an overly large length of the rcv software version.

Published: 2023-08-29 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-41361 is rated Moderate Risk (59.7/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.38%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-41361

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-22 0.50% 0.38% -0.12%
2 2025-11-21 0.94% 0.50% -0.45%
3 2025-11-18 — 0.94% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-41361

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2023-41361

OS Trackers for CVE-2023-41361

vendor priority summary link
debian unimportant CVE-2023-41361 unimportant priority: Debian including 1 source packages (frr), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2023-41361
redhat medium — https://access.redhat.com/security/cve/CVE-2023-41361
suse medium CVE-2023-41361 severity moderate: SUSE including 18 source package names (frr, frr-devel, …), 310 product×package rows across 35 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 7, … (35 product lines)): Known Not Affected 310. https://www.suse.com/security/cve/CVE-2023-41361/
ubuntu medium CVE-2023-41361 medium priority: Ubuntu including 2 source packages (frr, quagga), 16 status rows across 8 suites (bionic, focal, jammy, lunar, mantic, trusty, upstream, xenial): not-affected 7, ignored 4, DNE 3, needs-triage 2. https://ubuntu.com/security/CVE-2023-41361

Affected software / configurations for CVE-2023-41361

Vendor Product Version Raw CPE
frrouting frrouting <= 9.0 cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2023-41361

cvelogic Threat Intelligence