# CVE-2022-28493: Security feature bypass in n/a

> Attackers can enable the Telnet service on TOTOLINK CP900 devices, bypassing security controls to gain remote access.

- **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:** 23 Mar 2023
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-388p-85c7-wr6g

## What is CVE-2022-28493?

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

### Official description

A vulnerability in TOTOLINK CP900 V6.3c.566 allows attackers to start the Telnet service,

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

It affects 1 product.


Products: Totolink Cp900 Firmware.

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

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

## Is CVE-2022-28493 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28495](https://insights.sbomify.com/CVE-2022-28495/): Command injection in n/a (critical 9.8)
- [CVE-2022-28491](https://insights.sbomify.com/CVE-2022-28491/): Command injection in n/a (critical 9.8)
- [CVE-2022-28492](https://insights.sbomify.com/CVE-2022-28492/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-28494](https://insights.sbomify.com/CVE-2022-28494/): Command injection in n/a (critical 9.8)
- [CVE-2022-28496](https://insights.sbomify.com/CVE-2022-28496/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28493 is a critical vulnerability in n/a, published on 23 Mar 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-2022-28493 in the wild and no public exploit code.

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-28493/ (Markdown: https://insights.sbomify.com/CVE-2022-28493/index.md)
```

## Sources

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

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