CVE-2026-37228: n/a
FlexRIC v2.0.0 contains a reachable assertion in e2ap_recv_sctp_msg() (src/lib/ep/e2ap_ep.c). The function allocates a fixed 32KB receive buffer and enforces assert(rc < len) on the sctp_recvmsg() return value. A remote unauthenticated attacker can send a single SCTP message with payload >= 32,768 bytes to crash the near-RT RIC, iApp, E2 Agent, or xApp process via SIGABRT. No valid E2AP PDU is required. All four SCTP endpoint types (ports 36421 and 36422) share this vulnerable code path. In Release builds (NDEBUG), the stripped assertion leads to a signed-to-unsigned integer overflow and potential out-of-bounds read.
AI Analysis
Technical Summary
FlexRIC v2.0.0 contains a reachable assertion vulnerability in the e2ap_recv_sctp_msg() function located in src/lib/ep/e2ap_ep.c. The function allocates a fixed 32KB receive buffer and asserts that the return value from sctp_recvmsg() is less than the buffer length. A remote unauthenticated attacker can send an SCTP message with a payload size equal to or exceeding 32,768 bytes, causing the assertion to fail and crash the process with SIGABRT. This affects multiple SCTP endpoint types on ports 36421 and 36422. In release builds where assertions are stripped, a signed-to-unsigned integer overflow can occur, potentially leading to an out-of-bounds read. The vulnerability does not require a valid E2AP PDU to be exploited.
Potential Impact
An attacker can remotely cause a denial of service by crashing critical FlexRIC components (near-RT RIC, iApp, E2 Agent, or xApp processes) through sending a specially crafted SCTP message. This results in process termination via SIGABRT, causing service disruption. There is no indication of confidentiality or integrity impact. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider network-level controls to restrict or monitor SCTP traffic on ports 36421 and 36422 to prevent reception of oversized SCTP messages. Avoid exposing these services to untrusted networks. No official fix or temporary workaround has been documented at this time.
CVE-2026-37228: n/a
Description
FlexRIC v2.0.0 contains a reachable assertion in e2ap_recv_sctp_msg() (src/lib/ep/e2ap_ep.c). The function allocates a fixed 32KB receive buffer and enforces assert(rc < len) on the sctp_recvmsg() return value. A remote unauthenticated attacker can send a single SCTP message with payload >= 32,768 bytes to crash the near-RT RIC, iApp, E2 Agent, or xApp process via SIGABRT. No valid E2AP PDU is required. All four SCTP endpoint types (ports 36421 and 36422) share this vulnerable code path. In Release builds (NDEBUG), the stripped assertion leads to a signed-to-unsigned integer overflow and potential out-of-bounds read.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FlexRIC v2.0.0 contains a reachable assertion vulnerability in the e2ap_recv_sctp_msg() function located in src/lib/ep/e2ap_ep.c. The function allocates a fixed 32KB receive buffer and asserts that the return value from sctp_recvmsg() is less than the buffer length. A remote unauthenticated attacker can send an SCTP message with a payload size equal to or exceeding 32,768 bytes, causing the assertion to fail and crash the process with SIGABRT. This affects multiple SCTP endpoint types on ports 36421 and 36422. In release builds where assertions are stripped, a signed-to-unsigned integer overflow can occur, potentially leading to an out-of-bounds read. The vulnerability does not require a valid E2AP PDU to be exploited.
Potential Impact
An attacker can remotely cause a denial of service by crashing critical FlexRIC components (near-RT RIC, iApp, E2 Agent, or xApp processes) through sending a specially crafted SCTP message. This results in process termination via SIGABRT, causing service disruption. There is no indication of confidentiality or integrity impact. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider network-level controls to restrict or monitor SCTP traffic on ports 36421 and 36422 to prevent reception of oversized SCTP messages. Avoid exposing these services to untrusted networks. No official fix or temporary workaround has been documented at this time.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-04-06T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1de301e29bf47b503a4ec7
Added to database: 06/01/2026, 19:52:33 UTC
Last enriched: 06/08/2026, 20:52:12 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 59
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.