# CVE-2024-4813: Ruijie RG-UAC interface_commit.php os command injection

> Remote attackers can execute arbitrary OS commands via the name argument in interface_commit.php, requiring a patch.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 13 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-rmwv-r4r7-j48f

## What is CVE-2024-4813?

CVE-2024-4813 is a medium-severity command injection vulnerability in Ruijie RG-UAC, published on 13 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in Ruijie RG-UAC up to 20240506. Affected is an unknown function of the file /view/networkConfig/physicalInterface/interface_commit.php. The manipulation of the argument name leads to os command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. VDB-263934 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-4813?

It affects 27 products.


Products: Ruijie Rg-Uac 6000-Cc Firmware, Ruijie Rg-Uac 6000-E10 Firmware, Ruijie Rg-Uac 6000-E10c Firmware, Ruijie Rg-Uac 6000-E20 Firmware, Ruijie Rg-Uac 6000-E20c Firmware, Ruijie Rg-Uac 6000-E20m Firmware, Ruijie Rg-Uac 6000-E50 Firmware, Ruijie Rg-Uac 6000-E50c Firmware, Ruijie Rg-Uac 6000-E50m Firmware, Ruijie Rg-Uac 6000-Ea Firmware, Ruijie Rg-Uac 6000-Ei Firmware, Ruijie Rg-Uac 6000-Isg02 Firmware, Ruijie Rg-Uac 6000-Isg10 Firmware, Ruijie Rg-Uac 6000-Isg200 Firmware, Ruijie Rg-Uac 6000-Isg40 Firmware, Ruijie Rg-Uac 6000-Si Firmware, Ruijie Rg-Uac 6000-U3100 Firmware, Ruijie Rg-Uac 6000-U3210 Firmware, Ruijie Rg-Uac 6000-X100 Firmware, Ruijie Rg-Uac 6000-X100s Firmware and 7 more.

## How do I fix CVE-2024-4813?

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

## Is CVE-2024-4813 being exploited?

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

## Other vulnerabilities in Ruijie RG-UAC

- [CVE-2024-4814](https://insights.sbomify.com/CVE-2024-4814/): Ruijie RG-UAC static_route_edit_commit.php os command injection (medium 5.3)
- [CVE-2024-4815](https://insights.sbomify.com/CVE-2024-4815/): Ruijie RG-UAC detail.php os command injection (medium 5.3)
- [CVE-2024-4816](https://insights.sbomify.com/CVE-2024-4816/): Ruijie RG-UAC gre_add_commit.php os command injection (medium 5.3)
- [CVE-2024-5336](https://insights.sbomify.com/CVE-2024-5336/): Ruijie RG-UAC vlan_add_commit.php addVlan os command injection (medium 5.1)
- [CVE-2024-5337](https://insights.sbomify.com/CVE-2024-5337/): Ruijie RG-UAC user_commit.php os command injection (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4813 and fix it if it is affected.

What it is: CVE-2024-4813 is a medium-severity command injection vulnerability in Ruijie RG-UAC, published on 13 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4813 in the wild and no public exploit code.

Affected product: Ruijie RG-UAC. 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-2024-4813/ (Markdown: https://insights.sbomify.com/CVE-2024-4813/index.md)
```

## Sources

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

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