# CVE-2022-48113: Hardcoded credentials in n/a

> Unauthenticated attackers can access telnet and login as root using hardcoded credentials in TOTOLINK N200RE_v5 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:** 2 Feb 2023
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-fvv3-6hg7-8mrp

## What is CVE-2022-48113?

CVE-2022-48113 is a critical vulnerability in n/a, published on 2 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in TOTOLINK N200RE_v5 firmware V9.3.5u.6139 allows unauthenticated attackers to access the telnet service via a crafted POST request. Attackers are also able to leverage this vulnerability to login as root via hardcoded credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Totolink N200re-V5 Firmware.

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

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

## Is CVE-2022-48113 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48113 exists.

## Other vulnerabilities in n/a

- [CVE-2023-4746](https://insights.sbomify.com/CVE-2023-4746/): TOTOLINK N200RE V5 Validity_check format string (high 8.8)
- [CVE-2024-0942](https://insights.sbomify.com/CVE-2024-0942/): Totolink N200RE V5 cstecgi.cgi session expiration (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48113 is a critical vulnerability in n/a, published on 2 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48113 exists.

Affected product: n/a. 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-48113/ (Markdown: https://insights.sbomify.com/CVE-2022-48113/index.md)
```

## Sources

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

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