# CVE-2023-22918: Information disclosure in ATP series firmware

> Authenticated attackers can retrieve encrypted administrator information from Zyxel network devices via a CGI program vulnerability.

- **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:** 24 Apr 2023
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-q9h2-893q-85gq

## What is CVE-2023-22918?

CVE-2023-22918 is a medium-severity vulnerability in Zyxel ATP series firmware, published on 24 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A post-authentication information exposure vulnerability in the CGI program of Zyxel ATP series firmware versions 4.32 through 5.35, USG FLEX series firmware versions 4.50 through 5.35, USG FLEX 50(W) firmware versions 4.16 through 5.35, USG20(W)-VPN firmware versions 4.16 through 5.35, VPN series firmware versions 4.30 through 5.35, NWA110AX firmware version 6.50(ABTG.2) and earlier versions, WAC500 firmware version 6.50(ABVS.0) and earlier versions, and WAX510D firmware version 6.50(ABTF.2) and earlier versions, which could allow a remote authenticated attacker to retrieve encrypted information of the administrator on an affected device.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-22918?

It affects 51 products.


Products: Zyxel Atp100 Firmware, Zyxel Atp100w Firmware, Zyxel Atp200 Firmware, Zyxel Atp500 Firmware, Zyxel Atp700 Firmware, Zyxel Atp800 Firmware, Zyxel Nap203 Firmware, Zyxel Nap303 Firmware, Zyxel Nap353 Firmware, Zyxel Nwa110ax Firmware, Zyxel Nwa1123-Ac-Pro Firmware, Zyxel Nwa1123-Ac Hd Firmware, Zyxel Nwa1123acv3 Firmware, Zyxel Nwa210ax Firmware, Zyxel Nwa220ax-6e Firmware, Zyxel Nwa50ax-Pro Firmware, Zyxel Nwa50ax Firmware, Zyxel Nwa5123-Ac Hd Firmware, Zyxel Nwa55axe Firmware, Zyxel Nwa90ax-Pro Firmware and 31 more.

## How do I fix CVE-2023-22918?

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

## Is CVE-2023-22918 being exploited?

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

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

## Sources

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

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