# CVE-2022-0342: Auth bypass in ATP series firmware

> Attackers can bypass web authentication in Zyxel firewall firmware to gain administrative access to the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5g3j-g6gx-xfcg

## What is CVE-2022-0342?

CVE-2022-0342 is a critical authentication bypass vulnerability in Zyxel ATP series firmware, published on 28 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability in the CGI program of Zyxel USG/ZyWALL series firmware versions 4.20 through 4.70, USG FLEX series firmware versions 4.50 through 5.20, ATP series firmware versions 4.32 through 5.20, VPN series firmware versions 4.30 through 5.20, and NSG series firmware versions V1.20 through V1.33 Patch 4, which could allow an attacker to bypass the web authentication and obtain administrative access of the device.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-0342?

It affects 23 products.


Products: Zyxel Atp100 Firmware, Zyxel Atp100w Firmware, Zyxel Atp200 Firmware, Zyxel Atp500 Firmware, Zyxel Atp700 Firmware, Zyxel Atp800 Firmware, Zyxel Nsg300 Firmware, Zyxel Usg40 Firmware, Zyxel Usg40w Firmware, Zyxel Usg60 Firmware, Zyxel Usg60w Firmware, Zyxel Usg Flex 100 Firmware, Zyxel Usg Flex 100w Firmware, Zyxel Usg Flex 200 Firmware, Zyxel Usg Flex 500 Firmware, Zyxel Usg Flex 700 Firmware, Zyxel Vpn1000 Firmware, Zyxel Vpn100 Firmware, Zyxel Vpn300 Firmware, Zyxel Vpn50 Firmware and 3 more.

## How do I fix CVE-2022-0342?

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

## Is CVE-2022-0342 being exploited?

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

Public exploit code:

- Zyxel - Authentication Bypass (nuclei): http/cves/2022/CVE-2022-0342.yaml

## Other vulnerabilities in Zyxel ATP series 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-2022-0342 and fix it if it is affected.

What it is: CVE-2022-0342 is a critical authentication bypass vulnerability in Zyxel ATP series firmware, published on 28 Mar 2022. 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-2022-0342 exists.

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

## Sources

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

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