Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2024-55553

Quick assessment

Affected
n/a n/a
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

FRRouting是FRRouting开源的一种在类 Unix 平台上运行的网络路由软件套件。 FRRouting 10.3之前版本存在安全漏洞，该漏洞源于攻击者可以通过发送大约500个RPKI更新来触发重复的RIB重新验证，从而导致重新验证时间延长和拒绝服务。

AI Predicted 6.1 Difficulty: Easy EPSS 0.85% · P57
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-55553

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: CVE Program / CVE List V5
Vulnerability Description
In FRRouting (FRR) before 10.3 from 6.0 onward, all routes are re-validated if the total size of an update received via RTR exceeds the internal socket's buffer size, default 4K on most OSes. An attacker can use this to trigger re-parsing of the RIB for FRR routers using RTR by causing more than this number of updates during an update interval (usually 30 minutes). Additionally, this effect regularly occurs organically. Furthermore, an attacker can use this to trigger route validation continuously. Given that routers with large full tables may need more than 30 minutes to fully re-validate the table, continuous issuance/withdrawal of large numbers of ROA may be used to impact the route handling performance of all FRR instances using RPKI globally. Additionally, the re-validation will cause heightened BMP traffic to ingestors. Fixed Versions: 10.0.3, 10.1.2, 10.2.1, >= 10.3.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
FRRouting 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
FRRouting是FRRouting开源的一种在类 Unix 平台上运行的网络路由软件套件。 FRRouting 10.3之前版本存在安全漏洞，该漏洞源于攻击者可以通过发送大约500个RPKI更新来触发重复的RIB重新验证，从而导致重新验证时间延长和拒绝服务。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
- n/a n/a -

II. Public POCs for CVE-2024-55553

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-55553

请登录查看更多情报信息。

Patches & Fixes for CVE-2024-55553 (1)

Vendor Advisories for CVE-2024-55553 (1)

Same Patch Batch · n/a · 2025-01-06 · 25 CVEs total

CVE-2024-54767 AVM FRITZ!Box 7530 AX 安全漏洞
CVE-2021-27285 Inspur ClusterEngine 安全漏洞
CVE-2024-53935 Galaxy studio apps iCall OS17 Color Phone Flash 安全漏洞
CVE-2024-53932 BG.Studio Color Phone Call Screen App 安全漏洞
CVE-2024-53934 BG.Studio Color Phone Call Screen App 安全漏洞
CVE-2024-53931 Wallfinity: Lovely Caller Theme iCaller Caller Theme & Dialer 安全漏洞
CVE-2024-53933 HK DEVERLOP: Personalize Your World Call Theme & Call Screen 安全漏洞
CVE-2024-53936 BG.Studio Color Phone Call Screen App 安全漏洞
CVE-2024-46622 SecureAge Security Suite 安全漏洞
CVE-2024-46209 Yakamara Media Redaxo CMS 安全漏洞
CVE-2024-46073 Glacies IceHRM 安全漏洞
CVE-2024-54764 ipTIME A2004 安全漏洞
CVE-2024-35498 Grav 安全漏洞
CVE-2024-54880 SeaCMS 安全漏洞
CVE-2024-54879 SeaCMS 安全漏洞
CVE-2024-54763 ipTIME A2004 安全漏洞
CVE-2024-51112 PNETLab 安全漏洞
CVE-2024-51111 PNETLab 安全漏洞
CVE-2024-56828 ChestnutCMS 安全漏洞
CVE-2024-55407 ITE IO Access 安全漏洞

Showing top 20 of 25 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

Same product: n/a
Same vendor: n/a

V. Comments for CVE-2024-55553

No comments yet

Leave a comment