VulnerabilityPublished 29 Apr 2024Updated 6 Nov 2024

CVE-2024-34047: RicServiceUpdateHandler · O-RAN RIC I-Release e2mgr lacks array size checks

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should monitor vendor advisories for patches addressing CVE-2024-34047 and apply them promptly once available. In the interim, implement strict input validation and sanitization on all data processed by the RicServiceUpdateHandler to prevent malformed requests from triggering the vulnerability. Restrict network access to the e2mgr service using network segmentation, firewalls, and access control lists to limit exposure to trusted entities only. Employ runtime application self-protection (RASP) or intrusion detection systems capable of detecting anomalous requests targeting the RicServiceUpdateHandler. Conduct thorough code reviews and static analysis on the O-RAN RIC software to identify and remediate similar array bounds issues. Additionally, maintain comprehensive logging and monitoring of the e2mgr component to detect potential exploitation attempts. Collaborate with O-RAN community and vendors to share threat intelligence and best practices for securing open RAN deployments.

Description

O-RAN RIC I-Release e2mgr lacks array size checks in RicServiceUpdateHandler.

Impact

The primary impact of CVE-2024-34047 is on data integrity within the O-RAN RIC e2mgr component. Exploitation could lead to corrupted or manipulated data in the RicServiceUpdateHandler, potentially affecting the reliability of network control operations. While confidentiality and availability are not directly impacted, integrity issues in a critical network controller could indirectly degrade network performance or cause misconfigurations. Telecom operators relying on O-RAN RIC I-Release for network management may experience operational disruptions or degraded service quality if this vulnerability is exploited. The scope is limited to organizations deploying this specific open RAN software component, which is increasingly adopted in modern telecom networks aiming for vendor interoperability and flexibility. The absence of known exploits reduces immediate risk, but the vulnerability's presence in a critical telecom control plane component warrants proactive mitigation to prevent future exploitation. The medium CVSS score reflects moderate risk, balancing the limited impact scope with the ease of exploitation and network accessibility.

References

Community reviews

Loading reviews…