FRRouting < 10.5.3 Integer Overflow in OSPF TLV Parser Functions
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: FRRouting frr 10.5.3; azl3 frr 10.5.0-2 on Azure Linux 3.0 10.5.0-3; azl3 frr 10.5.0-3 on Azure Linux 3.0 10.5.0-3.
Low priority for now. Upgrade to FRRouting frr 10.5.3; azl3 frr 10.5.0-2 on Azure Linux 3.0 10.5.0-3; azl3 frr 10.5.0-3 on Azure Linux 3.0 10.5.0-3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
FRRouting before 10.5.3 contains an integer overflow vulnerability in seven OSPF Traffic Engineering and Segment Routing TLV parser functions where a uint16_t accumulator variable truncates uint32_t values returned by the TLV_SIZE() macro, causing the loop termination condition to fail while pointer advancement continues unchecked. Attackers with an established OSPF adjacency can send a crafted LS Update packet with a malicious Type 10 or Type 11 Opaque LSA to trigger out-of-bounds memory reads and crash all affected routers in the OSPF area or autonomous system.
- Published
- Apr 30, 2026
- Updated
- Oct 1, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-125
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 6.0
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| frrouting | frrouting | cpe:2.3:a:frrouting:frrouting |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- frrouting frroutingbefore 10.5.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
FRRouting frr
- before 10.5.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | frr | before 8.4.4-1.1~deb12u2 | 8.4.4-1.1~deb12u2 |
| Debian:13 | frr | before 10.3-3+deb13u1 | 10.3-3+deb13u1 |
| Debian:14 | frr | before 10.5.3-1 | 10.5.3-1 |
| openSUSE:Tumbleweed | frr | before 10.6.1-1.1 | 10.6.1-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | frr | before 7.4-150300.4.43.1 | 7.4-150300.4.43.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP7 | frr | before 8.5.7-150500.4.43.1 | 8.5.7-150500.4.43.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP7 | frr | before 10.2.6-150700.3.10.1 | 10.2.6-150700.3.10.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | frr | before 8.5.7-8.16.1 | 8.5.7-8.16.1 |
| SUSE:Linux Enterprise Server 16.0 | frr | before 10.2.6-160000.1.1 | 10.2.6-160000.1.1 |
Same product
frrouting: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-38406bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow."39Monitor
- CVE-2023-41361An issue was discovered in FRRouting FRR 9.0.39Monitor
- CVE-2022-37032An out-of-bounds read in the BGP daemon of FRRouting FRR before 8.4 may lead to a segmentation fault and denial of service.37Monitor
- CVE-2023-41360An issue was discovered in FRRouting FRR through 9.0.36Monitor
- CVE-2023-41359An issue was discovered in FRRouting FRR through 9.0.36Monitor
- CVE-2022-37035An issue was discovered in bgpd in FRRouting (FRR) 8.3.33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| FRRouting frr | 10.5.3 | Vendor (CNA) |
| azl3 frr 10.5.0-2 on Azure Linux 3.0 | 10.5.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 frr 10.5.0-3 on Azure Linux 3.0 | 10.5.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:frr | 8.4.4-1.1~deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:frr | 10.6.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:frr | 10.2.6-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Kazuma Matsumoto, a security researcherGMO Cybersecurity by IERAE, Inc.finder
- VulnCheckfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.