# CVE-2022-2030: Path traversal in ATP series firmware

> An authenticated attacker can exploit improper URL sanitization in CGI programs to access restricted files on Zyxel USG and ATP series devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 19 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cq2h-7r44-f9vg

## What is CVE-2022-2030?

CVE-2022-2030 is a medium-severity path traversal vulnerability in Zyxel ATP series firmware, published on 19 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A directory traversal vulnerability caused by specific character sequences within an improperly sanitized URL was identified in some CGI programs of Zyxel USG FLEX 100(W) firmware versions 4.50 through 5.30, USG FLEX 200 firmware versions 4.50 through 5.30, USG FLEX 500 firmware versions 4.50 through 5.30, USG FLEX 700 firmware versions 4.50 through 5.30, USG FLEX 50(W) firmware versions 4.16 through 5.30, USG20(W)-VPN firmware versions 4.16 through 5.30, ATP series firmware versions 4.32 through 5.30, VPN series firmware versions 4.30 through 5.30, USG/ZyWALL series firmware versions 4.11 through 4.72, that could allow an authenticated attacker to access some restricted files on a vulnerable device.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 25 products.


Products: Zyxel Atp100 Firmware, Zyxel Atp100w Firmware, Zyxel Atp200 Firmware, Zyxel Atp500 Firmware, Zyxel Atp700 Firmware, Zyxel Atp800 Firmware, Zyxel Usg20-Vpn Firmware, Zyxel Usg20w-Vpn Firmware, Zyxel Usg40 Firmware, Zyxel Usg40w Firmware, Zyxel Usg60 Firmware, Zyxel Usg60w Firmware, Zyxel Usg 2200-Vpn Firmware, Zyxel Usg Flex 100w Firmware, Zyxel Usg Flex 200 Firmware, Zyxel Usg Flex 500 Firmware, Zyxel Usg Flex 50w Firmware, Zyxel Usg Flex 700 Firmware, Zyxel Vpn1000 Firmware, Zyxel Vpn100 Firmware and 5 more.

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

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

## Is CVE-2022-2030 being exploited?

There is no known exploitation of CVE-2022-2030 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-2030 and fix it if it is affected.

What it is: CVE-2022-2030 is a medium-severity path traversal vulnerability in Zyxel ATP series firmware, published on 19 Jul 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-2030 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-2030/ (Markdown: https://insights.sbomify.com/CVE-2022-2030/index.md)
```

## Sources

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

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