# CVE-2023-6398: Command injection in NWA50AX firmware

> Authenticated administrators can execute OS commands via FTP in Zyxel network device firmware, requiring vendor patches.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2024
- **Updated:** 25 Aug 2024
- **Also known as:** GHSA-p6jh-65c7-8r26

## What is CVE-2023-6398?

CVE-2023-6398 is a high-severity command injection vulnerability in Zyxel  NWA50AX firmware, published on 20 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A post-authentication command injection vulnerability in the file upload binary in Zyxel ATP series firmware versions from 4.32 through 5.37 Patch 1, USG FLEX series firmware versions from 4.50 through 5.37 Patch 1, USG FLEX 50(W) series firmware versions from 4.16 through 5.37 Patch 1, USG20(W)-VPN series firmware versions from 4.16 through 5.37 Patch 1, 

USG FLEX H series firmware versions from 1.10 through 1.10 Patch 1,

NWA50AX firmware versions through 6.29(ABYW.3), WAC500 firmware versions through 6.65(ABVS.1), WAX300H firmware versions through 6.60(ACHF.1), and WBE660S firmware versions through 6.65(ACGG.1) could allow an authenticated attacker with administrator privileges to execute some operating system (OS) commands on an affected device via FTP.

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

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

It affects 42 products.


Products: Zyxel Atp100 Firmware, Zyxel Atp100w Firmware, Zyxel Atp200 Firmware, Zyxel Atp500 Firmware, Zyxel Atp700 Firmware, Zyxel Atp800 Firmware, Zyxel Nwa110ax Firmware, Zyxel Nwa1123acv3 Firmware, Zyxel Nwa210ax Firmware, Zyxel Nwa220ax-6e Firmware, Zyxel Nwa50ax-Pro Firmware, Zyxel Nwa50ax Firmware, Zyxel Nwa55axe Firmware, Zyxel Nwa90ax-Pro Firmware, Zyxel Nwa90ax Firmware, Zyxel Uos, Zyxel Usg20-Vpn Firmware, Zyxel Usg20w-Vpn Firmware, Zyxel Usg Flex 100 Firmware, Zyxel Usg Flex 100ax Firmware and 22 more.

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

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

## Is CVE-2023-6398 being exploited?

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

## Other vulnerabilities in Zyxel  NWA50AX firmware

- [CVE-2023-33009](https://insights.sbomify.com/CVE-2023-33009/): Zyxel Multiple Firewalls Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2023-33010](https://insights.sbomify.com/CVE-2023-33010/): Zyxel Multiple Firewalls Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2023-28771](https://insights.sbomify.com/CVE-2023-28771/): Zyxel Multiple Firewalls OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2022-30525](https://insights.sbomify.com/CVE-2022-30525/): Zyxel Multiple Firewalls OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2020-29583](https://insights.sbomify.com/CVE-2020-29583/): Zyxel Multiple Products Use of Hard-Coded Credentials (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6398 is a high-severity command injection vulnerability in Zyxel  NWA50AX firmware, published on 20 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6398 in the wild and no public exploit code.

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

## Sources

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

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