# CVE-2020-36870: Ruijie Gateway EG & NBR Models v11.1(6)B9P1 - 11.9(4)B12P1 RCE

> Attackers can execute arbitrary commands on Ruijie Gateways by exploiting front-end code when specific features like guest authentication are enabled.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-j892-g9v8-f728

## What is CVE-2020-36870?

CVE-2020-36870 is a critical code injection vulnerability in Beijing Star-Net Ruijie Network Technology Co., Ltd. EG3210, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Various Ruijie Gateway EG and NBR models firmware versions 11.1(6)B9P1 < 11.9(4)B12P1 contain a code execution vulnerability in the EWEB management system that can be abused via front-end functionality. Attackers can exploit front-end code when features such as guest authentication, local server authentication, or screen mirroring are enabled to gain access or execute commands on affected devices. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-02-05 UTC.

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

## Which versions are affected by CVE-2020-36870?


## How do I fix CVE-2020-36870?

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

## Is CVE-2020-36870 being exploited?

There is no known exploitation of CVE-2020-36870 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36870 and fix it if it is affected.

What it is: CVE-2020-36870 is a critical code injection vulnerability in Beijing Star-Net Ruijie Network Technology Co., Ltd. EG3210, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36870 in the wild and no public exploit code.

Affected product: Beijing Star-Net Ruijie Network Technology Co., Ltd. EG3210. 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-2020-36870/ (Markdown: https://insights.sbomify.com/CVE-2020-36870/index.md)
```

## Sources

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

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