# CVE-2023-34138: Command injection in ATP series firmware

> An unauthenticated LAN attacker can execute OS commands on Zyxel firewalls if an admin adds their IP to trusted RADIUS clients.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2023
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-886j-wm8v-5q3q

## What is CVE-2023-34138?

CVE-2023-34138 is a high-severity command injection vulnerability in Zyxel ATP series firmware, published on 17 Jul 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A command injection vulnerability in the hotspot management feature of the Zyxel ATP series firmware versions 4.60 through 5.36 Patch 2, USG FLEX series firmware versions 4.60 through 5.36 Patch 2,  USG FLEX 50(W) series firmware versions 4.60 through 5.36 Patch 2, USG20(W)-VPN series firmware versions 4.60 through 5.36 Patch 2, and VPN series firmware versions 4.60 through 5.36 Patch 2, could allow an unauthenticated, LAN-based attacker to execute some OS commands on an affected device if the attacker could trick an authorized administrator to add their IP address to the list of trusted RADIUS clients in advance.

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

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

It affects 22 products.


Products: Zyxel Usg 20w-Vpn Firmware, Zyxel Usg 2200-Vpn Firmware, Zyxel Usg Flex 100 Firmware, Zyxel Usg Flex 100w Firmware, Zyxel Usg Flex 200 Firmware, Zyxel Usg Flex 500 Firmware, Zyxel Usg Flex 50 Firmware, Zyxel Usg Flex 50w Firmware, Zyxel Usg Flex 700 Firmware, Zyxel Zywall Atp100 Firmware, Zyxel Zywall Atp100w Firmware, Zyxel Zywall Atp200 Firmware, Zyxel Zywall Atp500 Firmware, Zyxel Zywall Atp700 Firmware, Zyxel Zywall Atp800 Firmware, Zyxel Zywall Vpn100 Firmware, Zyxel Zywall Vpn2s Firmware, Zyxel Zywall Vpn300 Firmware, Zyxel Zywall Vpn50 Firmware, Zyxel Zywall Vpn 100 Firmware and 2 more.

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

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

## Is CVE-2023-34138 being exploited?

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

## Other vulnerabilities in Zyxel ATP series firmware

- [CVE-2023-28767](https://insights.sbomify.com/CVE-2023-28767/): Command injection in ATP series firmware (high 8.8)
- [CVE-2023-33011](https://insights.sbomify.com/CVE-2023-33011/): Command injection in ATP series firmware (high 8.8)
- [CVE-2023-33012](https://insights.sbomify.com/CVE-2023-33012/): Command injection in ATP series firmware (high 8.8)
- [CVE-2023-22915](https://insights.sbomify.com/CVE-2023-22915/): Memory corruption in USG FLEX 50(W) firmware (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34138 is a high-severity command injection vulnerability in Zyxel ATP series firmware, published on 17 Jul 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-34138 in the wild and no public exploit code.

Affected product: Zyxel ATP series firmware. 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-34138/ (Markdown: https://insights.sbomify.com/CVE-2023-34138/index.md)
```

## Sources

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

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