CVE-2024-31950

In FRRouting (FRR) through 9.1, there can be a buffer overflow and daemon crash in ospf_te_parse_ri for OSPF LSA packets during an attempt to read Segment Routing subTLVs (their size is not validated).

Published: 2024-04-07 Last update: 2025-05-01 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-31950 is rated Moderate Risk (45.6/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.33%). 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-2024-31950

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-21 0.17% 0.33% +0.16%
2 2025-11-18 0.28% 0.17% -0.10%
3 2025-08-27 — 0.28% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-31950

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N 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:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-31950

OS Trackers for CVE-2024-31950

vendor priority summary link
debian unimportant CVE-2024-31950 unimportant priority: Debian including 1 source packages (frr), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-31950
redhat medium — https://access.redhat.com/security/cve/CVE-2024-31950
suse high CVE-2024-31950 severity important: SUSE including 58 source package names (frr, frr-10.2.1-150700.1.7, …), 365 product×package rows across 34 product lines (SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 12 SP5, … (34 product lines)): Known Not Affected 294, Fixed 71. https://www.suse.com/security/cve/CVE-2024-31950/
ubuntu medium CVE-2024-31950 medium priority: Ubuntu including 2 source packages (frr, quagga), 12 status rows across 7 suites (bionic, focal, jammy, mantic, noble, upstream, xenial): not-affected 4, DNE 3, released 3, needs-triage 2. https://ubuntu.com/security/CVE-2024-31950

Affected software / configurations for CVE-2024-31950

Vendor Product Version Raw CPE
frrouting frrouting <= 9.1 cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*

References for CVE-2024-31950

cvelogic Threat Intelligence