CVE-2024-34049VulnerabilityPublished 29 Apr 2024Updated 20 Aug 2024

CVE-2024-34049: rimedo-ts · n/a

Affects rimedo-tsSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 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 45% 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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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 2026-10-25.

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 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

Affected software

Product	Affected	Fixed in
GitHubonosproject/rimedo-ts`pkg:github/onosproject/rimedo-ts`Other threats	Affected =0.1.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-34049, organizations should first verify if they are running the affected rimedo-ts 0.1.1 version within their SD-RAN deployments. Immediate mitigation steps include: 1) Implement input validation to ensure that plmnIdString inputs are at least three characters long before slicing; this can be done by patching the source code to add boundary checks prior to slicing operations. 2) Deploy runtime monitoring and anomaly detection to identify and alert on unexpected crashes or panics in the rimedo-ts process. 3) Use process supervision and automatic restart mechanisms to minimize downtime caused by crashes. 4) Engage with the Open Networking Foundation or software maintainers to obtain patches or updates addressing this vulnerability as soon as they are released. 5) Restrict network access to the affected component to trusted sources only, reducing exposure to remote exploitation attempts. 6) Conduct thorough testing of inputs in staging environments to detect similar out-of-bounds issues proactively. 7) Maintain up-to-date backups and incident response plans to recover quickly from potential service disruptions. These steps go beyond generic advice by focusing on code-level validation, operational monitoring, and network-level access controls specific to the nature of this vulnerability.

Description

Open Networking Foundation SD-RAN Rimedo rimedo-ts 0.1.1 has a slice bounds out-of-range panic in "return plmnIdString[0:3], plmnIdString[3:]" in reader.go.

Impact

The primary impact of CVE-2024-34049 is a denial-of-service condition caused by a crash of the SD-RAN Rimedo rimedo-ts process. This can disrupt telecom network operations relying on this software, potentially leading to partial or complete loss of radio access network services. Since SD-RAN components are integral to managing and orchestrating radio access in 4G/5G networks, service outages could affect large numbers of end users, degrade network reliability, and impact critical communications. The vulnerability does not affect confidentiality or integrity, but availability degradation in telecom infrastructure can have cascading effects on emergency services, enterprise communications, and consumer connectivity. Organizations deploying SD-RAN solutions from the Open Networking Foundation or using rimedo-ts 0.1.1 should consider this a high-priority risk. The lack of authentication or user interaction requirements makes exploitation easier for attackers scanning for vulnerable instances. Although no active exploits are known, the potential for automated attacks exists once details become public. The impact is especially critical for telecom operators and service providers who rely on continuous network uptime.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/onosproject/rimedo-ts/issues/16 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 04:39 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats