# CVE-2023-27796: Command injection in n/a

> Attackers can execute arbitrary commands on Ruijie wireless routers via the diagnose.lua script, potentially compromising the device.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2023
- **Updated:** 20 Feb 2025
- **Also known as:** GHSA-wcvw-xvmj-6fw7

## What is CVE-2023-27796?

CVE-2023-27796 is a high-severity command injection vulnerability in n/a, published on 26 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RG-EW1200G PRO Wireless Routers EW_3.0(1)B11P204, RG-EW1800GX PRO Wireless Routers EW_3.0(1)B11P204, and RG-EW3200GX PRO Wireless Routers EW_3.0(1)B11P204 were discovered to contain multiple command injection vulnerabilities via the data.ip, data.protocal, data.iface and data.package parameters in the runPackDiagnose function of diagnose.lua.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2023-27796?

It affects 3 products.


Products: Ruijienetworks Rg-Ew1200g Pro Firmware, Ruijienetworks Rg-Ew1800gx Pro Firmware, Ruijienetworks Rg-Ew3200gx Pro Firmware.

## How do I fix CVE-2023-27796?

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

## Is CVE-2023-27796 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27796 and fix it if it is affected.

What it is: CVE-2023-27796 is a high-severity command injection vulnerability in n/a, published on 26 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27796 in the wild and no public exploit code.

Affected product: n/a. 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-2023-27796/ (Markdown: https://insights.sbomify.com/CVE-2023-27796/index.md)
```

## Sources

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

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