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

> A local attacker can execute arbitrary code on TRENDnet TEW-822DRE routers via the ipv4_ping parameter in the system check form.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-cj4v-q99x-3m3c

## What is CVE-2023-51835?

CVE-2023-51835 is a medium-severity command injection vulnerability in n/a, published on 1 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in TRENDnet TEW-822DRE v.1.03B02 allows a local attacker to execute arbitrary code via the parameters ipv4_ping in the /boafrm/formSystemCheck.

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

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

It affects 1 product.


Products: Trendnet Tew-822dre Firmware.

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

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

## Is CVE-2023-51835 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51835 exists.

## Other vulnerabilities in n/a

- [CVE-2024-0920](https://insights.sbomify.com/CVE-2024-0920/): TRENDnet TEW-822DRE POST Request admin_ping.htm command injection (high 7.2)
- [CVE-2025-15139](https://insights.sbomify.com/CVE-2025-15139/): TRENDnet TEW-822DRE formWsc sub_43ACF4 command injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51835 is a medium-severity command injection vulnerability in n/a, published on 1 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51835 exists.

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-51835/ (Markdown: https://insights.sbomify.com/CVE-2023-51835/index.md)
```

## Sources

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

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