# CVE-2020-29299: Command injection in n/a

> An admin can execute arbitrary commands via the password change interface in various Zyxel network devices.

- **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:** 27 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g8hw-8grv-27jh

## What is CVE-2020-29299?

CVE-2020-29299 is a high-severity command injection vulnerability in n/a, published on 27 Dec 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Certain Zyxel products allow command injection by an admin via an input string to chg_exp_pwd during a password-change action. This affects VPN On-premise before ZLD V4.39 week38, VPN Orchestrator before SD-OS V10.03 week32, USG before ZLD V4.39 week38, USG FLEX before ZLD V4.55 week38, ATP before ZLD V4.55 week38, and NSG before 1.33 patch 4.

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

## Which versions are affected by CVE-2020-29299?

It affects 4 products.


Products: Zyxel Nsg Firmware, Zyxel Usg Flex Firmware, Zyxel Vpn Orchestrator, Zyxel Zld.

## How do I fix CVE-2020-29299?

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

## Is CVE-2020-29299 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-29299 and fix it if it is affected.

What it is: CVE-2020-29299 is a high-severity command injection vulnerability in n/a, published on 27 Dec 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-29299 in the wild and no public exploit code.

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

## Sources

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

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