dbcve.org
Code InjectionWeakness · CWE-94

CVE-2020-36870

CRITICAL · 9.2 CVSS v4.0 Published 2025-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in the EWEB management system of Ruijie Gateway EG and NBR devices. Attackers can execute arbitrary commands through front-end functionality when guest authentication, local server authentication, or screen mirroring features are enabled. The vulnerability affects firmware versions between 11.1(6)B9P1 and 11.9(4)B12P1 (excluding the patched version).

MitigationUpgrade Ruijie EG and NBR firmware to version 11.9(4)B12P1 or later. Until patching is possible, disable guest authentication, local server authentication, and screen mirroring features, and restrict management interface access to trusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model and firmware version
    Access the device's web management interface (EWEB) or CLI and locate the system information or firmware version display. This is typically found in the web UI under System Status or in CLI via 'show version' or 'show system-info'.
    Affected if The firmware version falls within the range 11.1(6)B9P1 to 11.9(4)B12P1 (any version before 11.9(4)B12P1).
  2. Confirm EWEB management interface is accessible
    Verify the EWEB management interface is reachable on the device. This is typically accessible via HTTP/HTTPS on the management IP of the gateway.
    Affected if The EWEB interface is exposed and accessible, particularly from untrusted networks.
  3. Check if guest authentication feature is enabled
    Log into EWEB and navigate to the authentication or guest settings configuration panel. Look for options related to 'Guest Authentication' or 'Guest Portal' in the network authentication settings.
    Affected if Guest authentication is enabled and allows access through the EWEB management system.
  4. Check if local server authentication is enabled
    In EWEB, locate the authentication server settings. Look for 'Local Server Authentication' or local user database configuration under the authentication or access control settings.
    Affected if Local server authentication is enabled as an authentication method.
  5. Check if screen mirroring feature is enabled
    In EWEB, search for 'Screen Mirroring' or display/casting settings. This feature may be found under network services, guest services, or display configuration menus.
    Affected if Screen mirroring is enabled on the device.

A device is affected if it runs firmware version 11.1(6)B9P1 through 11.9(4)B12P1 AND has at least one of the three vulnerable features (guest authentication, local server authentication, or screen mirroring) enabled in the EWEB management system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Ruijie EG and NBR firmware to version 11.9(4)B12P1 or later. Until patching is possible, disable guest authentication, local server authentication, and screen mirroring features, and restrict management interface access to trusted networks.

Recommended fix High confidence

Ruijie firmware 11.9(4)B12P1 or later for EG and NBR series

  1. 1. Identify the Ruijie device model (EG or NBR series) and current firmware version via the EWEB management interface or CLI using 'show version'
  2. 2. Confirm the current firmware version is below 11.9(4)B12P1 (vulnerable range: 11.1(6)B9P1 to versions before 11.9(4)B12P1)
  3. 3. Download firmware version 11.9(4)B12P1 or later from the official Ruijie support portal (www.ruijie.com.cn)
  4. 4. Back up the current device configuration through the EWEB management interface or CLI
  5. 5. Upload the fixed firmware via the EWEB management system under System Management > Firmware Upgrade, or via CLI using firmware upgrade commands
  6. 6. Reboot the device as prompted after firmware upload completes
  7. 7. After reboot, verify the new firmware version is 11.9(4)B12P1 or higher using 'show version'
  8. 8. Restore the backed-up configuration if not automatically preserved
Caveat Standard firmware upgrade risks apply - ensure configuration backup before upgrading; test in non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-36870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-36870 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data