# CVE-2023-22920: Misconfiguration in LTE3316-M604

> A remote attacker can access the Zyxel LTE3316-M604 router via Telnet due to a factory default testing misconfiguration.

- **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:** 21 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-wpqc-593w-375g

## What is CVE-2023-22920?

CVE-2023-22920 is a critical vulnerability in Zyxel LTE3316-M604, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security misconfiguration vulnerability exists in the Zyxel LTE3316-M604 firmware version V2.00(ABMP.6)C0 due to a factory default misconfiguration intended for testing purposes. A remote attacker could leverage this vulnerability to access an affected device using Telnet.

Weakness: CWE-284 (Improper Access Control)

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

It affects 2 products.


Products: Zyxel Lte3202-M437 Firmware, Zyxel Lte3316-M604 Firmware.

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

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

## Is CVE-2023-22920 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22920 and fix it if it is affected.

What it is: CVE-2023-22920 is a critical vulnerability in Zyxel LTE3316-M604, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22920 in the wild and no public exploit code.

Affected product: Zyxel LTE3316-M604. 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-22920/ (Markdown: https://insights.sbomify.com/CVE-2023-22920/index.md)
```

## Sources

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

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