CVE-2021-43160: A Remote Code Execution (RCE) vulnerability exists in Ruijie Networks Ruijie RG-EW Series Routers up to Rey...
A Remote Code Execution (RCE) vulnerability exists in Ruijie Networks Ruijie RG-EW Series Routers up to ReyeeOS 1.55.1915 / EW_3.0(1)B11P55 via the switchFastDhcp function in /cgi-bin/luci/api/diagnose.
Security readout for executives and security teams
Plain-English summary
CVE-2021-43160 is a remote code execution issue in Ruijie Networks RG-EW Series routers running ReyeeOS up to 1.55.1915 / EW_3.0(1)B11P55. If exploitable in a deployed environment, an attacker could potentially run code on the router. Sources do not provide a CVSS score, confirmed exploitation, or a named vendor fix.
Executive priority
Prioritize discovery and exposure reduction, especially for internet-facing routers. The issue is potentially severe because it involves remote code execution on network infrastructure, but public sources here lack CVSS, confirmed exploitation, and a specific patch version.
Technical view
The CVE describes RCE via the switchFastDhcp function in /cgi-bin/luci/api/diagnose on Ruijie RG-EW Series routers up to ReyeeOS 1.55.1915 / EW_3.0(1)B11P55. Public details are limited in the source bundle. Authentication requirements, affected model list, and remediation version are not specified in the provided CVE data.
Likely exposure
Exposure is most likely where affected Ruijie RG-EW Series router management interfaces are reachable from untrusted networks. Risk is lower if management access is restricted, but still relevant for internal attackers or compromised adjacent systems. Confirm exact models and firmware locally because the CVE record’s affected product metadata is incomplete.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. A public Full Disclosure reference exists, so vulnerability details may be publicly available. Do not assume exploitation is occurring without additional intelligence, but treat exposed management interfaces as urgent to review.
Researcher notes
Key gaps: incomplete affected product metadata, no CVSS, unclear authentication requirements, and no remediation version in provided sources. Validate against primary vendor materials before making broad exposure claims. Avoid relying solely on generic CPE data, which is absent in the CVE bundle.
Mitigation direction
Identify Ruijie RG-EW Series routers and record ReyeeOS or EW firmware versions.
Check Ruijie vendor guidance for fixed firmware or official mitigation.
Restrict router management interfaces to trusted administrative networks only.
Block internet access to /cgi-bin/luci management endpoints where possible.
Monitor router logs and network traffic for suspicious management activity.
Validation and detection
Inventory all Ruijie RG-EW devices in scope.
Compare firmware against ReyeeOS 1.55.1915 / EW_3.0(1)B11P55 threshold.
Verify management interfaces are not internet-exposed.
Confirm whether vendor firmware updates or advisories apply to each model.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
description · low confidence lookup
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
2Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 4, 2022, 00:08 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.