# CVE-2022-40602: Hardcoded credentials in LTE3301-M209

> Remote attackers can access the device using a pre-configured password if remote administration is enabled, requiring an upgrade to secure the firmware.

- **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:** 22 Nov 2022
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-rvh6-5433-qq87

## What is CVE-2022-40602?

CVE-2022-40602 is a critical vulnerability in Zyxel LTE3301-M209, published on 22 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw in the Zyxel LTE3301-M209 firmware verisons prior to V1.00(ABLG.6)C0 could allow a remote attacker to access the device using an improper pre-configured password if the remote administration feature has been enabled by an authenticated administrator.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Zyxel Lte3301-M209 Firmware.

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

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

## Is CVE-2022-40602 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40602 and fix it if it is affected.

What it is: CVE-2022-40602 is a critical vulnerability in Zyxel LTE3301-M209, published on 22 Nov 2022. 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-2022-40602 in the wild and no public exploit code.

Affected product: Zyxel LTE3301-M209. 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-40602/ (Markdown: https://insights.sbomify.com/CVE-2022-40602/index.md)
```

## Sources

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

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