rg-ew1200: Improper Control of Generation of Code
CVE-2023-34644 is a critical-severity improper control of generation of code vulnerability in rg-ew1200 from Ruijienetworks, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected rg-ew1200 versions: EW_3.0(1)B11P204. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.81% chance of exploitation within 30 days, higher than 79% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of rg-ew1200 you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on ruijie.com.cn for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Ruijienetworks | rg-ew1200 | EW_3.0(1)B11P204 | Not stated |
| Ruijienetworks | rg-s1930 | SWITCH_3.0(1)B11P218 | Not stated |
| Ruijienetworks | rg-eg350 | EG_3.0(1)B11P216 | Not stated |
| Ruijienetworks | eap | AP_3.0(1)B11P218 | Not stated |
| Ruijienetworks | rap | AP_3.0(1)B11P218 | Not stated |
| Ruijienetworks | nbc | AC_3.0(1)B11P86 | Not stated |
| Ruijie | Rg-ew1200r Firmware | 3.0\(1\)b11p204 | Not stated |
| Ruijie | Rg-ew300 Firmware | 3.0\(1\)b11p204 | Not stated |
| Ruijie | Rg-ew3200gx Firmware | 3.0\(1\)b11p204 | Not stated |
| Ruijie | Rg-ew1200g Firmware | 3.0\(1\)b11p204 | Not stated |
| Ruijie | Rg-ew1800gx Firmware | 3.0\(1\)b11p204 | Not stated |
| Ruijie | Rg-ew300r Firmware | 3.0\(1\)b11p204 | Not stated |
| Ruijie | Rg-ew1200 Firmware | 3.0\(1\)b11p204 | Not stated |
| Ruijie | Rg-eg3000xe Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg105g Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg305gh-p-e Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg105g-p Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg3230 Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg1000e Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg105g-e Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg105gw(t) Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg105gw-x Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg2000ce Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg2100-p Firmware | 3.0\(1\)b11p216 | Not stated |
| Ruijie | Rg-eg209gs Firmware | 3.0\(1\)b11p216 | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
Remote code execution vulnerability in Ruijie Networks Product: RG-EW series home routers and repeaters EW_3.0(1)B11P204, RG-NBS and RG-S1930 series switches SWITCH_3.0(1)B11P218, RG-EG series business VPN routers EG_3.0(1)B11P216, EAP and RAP series wireless access points AP_3.0(1)B11P218, NBC series wireless controllers AC_3.0(1)B11P86 allows unauthorized remote attackers to gain the highest privileges via crafted POST request to /cgi-bin/luci/api/auth.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Recent Improper Control of Generation of Code vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.