Skip to main content
VulnerabilityPublished Updated

CVE-2024-34046: Unthrottled Resource Allocation

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-34046, organizations should first monitor vendor advisories for patches or updates addressing the pointer dereference issue in the O-RAN E2T software. In the absence of patches, applying network-level protections such as filtering or rate limiting SCTP traffic to and from O-RAN E2T components can reduce exposure. Implementing robust monitoring for abnormal process crashes or service interruptions related to O-RAN E2T metrics can provide early detection of exploitation attempts. Network segmentation to isolate O-RAN E2T systems from untrusted networks will limit attack surface. Additionally, conducting thorough code reviews and static analysis on the affected source files (e.g., sctpThread.cpp) can help identify and remediate similar resource management issues proactively. Telecom operators should engage with O-RAN Alliance and vendors to prioritize secure coding practices and timely vulnerability disclosures. Finally, maintaining up-to-date incident response plans tailored to telecom infrastructure will improve resilience against denial of service attacks.

Description

The O-RAN E2T I-Release Prometheus metric Increment function can crash in sctpThread.cpp for message.peerInfo->sctpParams->e2tCounters[IN_SUCC][MSG_COUNTER][ProcedureCode_id_RICsubscription]->Increment().

References

Community reviews

Loading reviews…