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

> Authenticated attackers can bypass two-factor authentication to access IPsec VPN servers on Zyxel firewalls.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-mv2h-6cx9-44g2

## What is CVE-2022-0910?

CVE-2022-0910 is a medium-severity authentication bypass vulnerability in Zyxel ATP series firmware, published on 24 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A downgrade from two-factor authentication to one-factor authentication vulnerability in the CGI program of Zyxel USG/ZyWALL series firmware versions 4.32 through 4.71, USG FLEX series firmware versions 4.50 through 5.21, ATP series firmware versions 4.32 through 5.21, and VPN series firmware versions 4.32 through 5.21, that could allow an authenticated attacker to bypass the second authentication phase to connect the IPsec VPN server even though the two-factor authentication (2FA) was enabled.

Weakness: CWE-287 (Improper Authentication)

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

It affects 32 products.


Products: Zyxel Atp100 Firmware, Zyxel Atp100w Firmware, Zyxel Atp200 Firmware, Zyxel Atp500 Firmware, Zyxel Atp700 Firmware, Zyxel Atp800 Firmware, Zyxel Usg200 Firmware, Zyxel Usg20 Firmware, Zyxel Usg210 Firmware, Zyxel Usg2200 Firmware, Zyxel Usg300 Firmware, Zyxel Usg310 Firmware, Zyxel Usg 1100 Firmware, Zyxel Usg 110 Firmware, Zyxel Usg 1900 Firmware, Zyxel Usg 20w-Vpn Firmware, Zyxel Usg 20w Firmware, Zyxel Usg 2200-Vpn Firmware, Zyxel Usg 310 Firmware, Zyxel Usg 40 Firmware and 12 more.

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

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

## Is CVE-2022-0910 being exploited?

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

## 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-0910 and fix it if it is affected.

What it is: CVE-2022-0910 is a medium-severity authentication bypass vulnerability in Zyxel ATP series firmware, published on 24 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0910 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-2022-0910/ (Markdown: https://insights.sbomify.com/CVE-2022-0910/index.md)
```

## Sources

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

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