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

> An authenticated attacker can execute arbitrary commands on TP-Link TL-ER5120G routers by injecting code into NAPT rule names.

- **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:** 20 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-g567-mjjp-5vw4

## What is CVE-2023-43138?

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

### Official description

TPLINK TL-ER5120G 4.0 2.0.0 Build 210817 Rel.80868n has a command injection vulnerability, when an attacker adds NAPT rules after authentication, and the rule name has an injection point.

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

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

It affects 1 product.


Products: Tp-Link Tl-Er5120g Firmware.

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

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

## Is CVE-2023-43138 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-43135](https://insights.sbomify.com/CVE-2023-43135/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-43137](https://insights.sbomify.com/CVE-2023-43137/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43138 is a high-severity command injection vulnerability in n/a, published on 20 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43138 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-43138/ (Markdown: https://insights.sbomify.com/CVE-2023-43138/index.md)
```

## Sources

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

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