# CVE-2024-42936: Code injection in n/a

> Attackers can execute arbitrary code on Ruijie RG-EW300N routers by sending modified MQTT broker messages to the mqlink.elf service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-25fh-589c-4pcj

## What is CVE-2024-42936?

CVE-2024-42936 is a critical code injection vulnerability in n/a, published on 21 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The mqlink.elf is service component in Ruijie RG-EW300N with firmware ReyeeOS 1.300.1422 is vulnerable to Remote Code Execution via a modified MQTT broker message.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-42936?

It affects 1 product.


Products: Ruijie Reyee Os.

## How do I fix CVE-2024-42936?

No fix has been published for CVE-2024-42936 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-42936 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42936 exists.

## Other vulnerabilities in n/a

- [CVE-2025-56083](https://insights.sbomify.com/CVE-2025-56083/): Command injection in n/a (high 8.8)
- [CVE-2025-56084](https://insights.sbomify.com/CVE-2025-56084/): Command injection in n/a (high 8.8)
- [CVE-2025-56099](https://insights.sbomify.com/CVE-2025-56099/): Command injection in n/a (high 8.8)
- [CVE-2025-56113](https://insights.sbomify.com/CVE-2025-56113/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42936 and fix it if it is affected.

What it is: CVE-2024-42936 is a critical code injection vulnerability in n/a, published on 21 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42936 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-42936/ (Markdown: https://insights.sbomify.com/CVE-2024-42936/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42936
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42936
- OSV: https://osv.dev/vulnerability/CVE-2024-42936

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-42936/
Summaries are generated and may contain mistakes; the official description above is the record.