# CVE-2024-8234: Command injection in NWA1100-N firmware

> Unauthenticated attackers can execute OS commands on unsupported Zyxel NWA1100-N devices to access system files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2024
- **Updated:** 30 Aug 2024
- **Also known as:** GHSA-wfxq-5cv4-254v

## What is CVE-2024-8234?

CVE-2024-8234 is a high-severity command injection vulnerability in Zyxel NWA1100-N firmware, published on 30 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

** UNSUPPORTED WHEN ASSIGNED ** A command injection vulnerability in the functions formSysCmd(), formUpgradeCert(), and formDelcert() in the Zyxel NWA1100-N firmware version 1.00(AACE.1)C0 could allow an unauthenticated attacker to execute some OS commands to access system files on an affected device.

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

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

It affects 1 product.


Products: Zyxel Nwaw1100-N Firmware.

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

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

## Is CVE-2024-8234 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8234 is a high-severity command injection vulnerability in Zyxel NWA1100-N firmware, published on 30 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8234 exists.

Affected product: Zyxel NWA1100-N 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-2024-8234/ (Markdown: https://insights.sbomify.com/CVE-2024-8234/index.md)
```

## Sources

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

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