CVE-2021-43161: 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 doSwitchApi function in /cgi-bin/luci/api/switch.
Security readout for executives and security teams
Plain-English summary
CVE-2021-43161 is a reported remote code execution flaw in Ruijie Networks RG-EW Series routers. Affected firmware is listed up to ReyeeOS 1.55.1915 / EW_3.0(1)B11P55. If an attacker can reach the vulnerable management endpoint, compromise of the router may be possible. Public sources do not confirm active exploitation or a vendor fix.
Executive priority
Treat this as a high-priority edge-device risk if Ruijie RG-EW routers are deployed. Routers sit at network boundaries, and RCE can enable broader compromise. Prioritize inventory, exposure reduction, and vendor firmware review.
Technical view
The CVE describes RCE through the doSwitchApi function at /cgi-bin/luci/api/switch on Ruijie RG-EW Series routers up to ReyeeOS 1.55.1915 / EW_3.0(1)B11P55. The record has no CVSS score, CWE, or structured CPE data. The primary public reference is a Full Disclosure post.
Likely exposure
Exposure is likely limited to environments using Ruijie RG-EW Series routers on the affected firmware. Risk increases if router administration interfaces or related LuCI API paths are reachable from untrusted networks, partner networks, or the internet.
Exploitation context
The public record describes remote code execution, but CISA KEV does not list this CVE and the provided sources do not state active exploitation. A public disclosure exists, so defenders should assume technical details may be available to researchers and attackers.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, or vendor advisory is included in the supplied sources. The affected range and vulnerable function come from the CVE description and disclosure reference. Avoid assuming exploit-in-the-wild or patch availability without additional vendor confirmation.
Mitigation direction
Identify Ruijie RG-EW Series routers in inventory.
Check firmware against ReyeeOS 1.55.1915 / EW_3.0(1)B11P55.
Review Ruijie guidance for fixed firmware or official mitigation.
Restrict router management access to trusted administrative networks.
Block internet exposure of management and LuCI API interfaces.
Monitor router logs for unexpected administrative or API activity.
Validation and detection
Confirm model and firmware from device administration records.
Verify whether management interfaces are reachable from untrusted networks.
Check exposure through external attack surface management scans.
Review logs for unusual access to LuCI API paths.
Document remediation status for each affected router.
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.