# CVE-2024-34219: Hardcoded credentials in n/a

> Attackers can exploit hardcoded credentials in the SetTelnetCfg function to gain unauthorized telnet access to TOTOLINK CP450 routers.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-24qq-8vc9-wp3m

## What is CVE-2024-34219?

CVE-2024-34219 is a high-severity vulnerability in n/a, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOTOLINK CP450 V4.1.0cu.747_B20191224 was discovered to contain a vulnerability in the SetTelnetCfg function, which allows attackers to log in through telnet.

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

## Which versions are affected by CVE-2024-34219?

It affects 1 product.


Products: Totolink Cp450 Firmware.

## How do I fix CVE-2024-34219?

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

## Is CVE-2024-34219 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-34204](https://insights.sbomify.com/CVE-2024-34204/): Command injection in n/a (critical 9.8)
- [CVE-2024-34209](https://insights.sbomify.com/CVE-2024-34209/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-34213](https://insights.sbomify.com/CVE-2024-34213/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-7332](https://insights.sbomify.com/CVE-2024-7332/): TOTOLINK CP450 Telnet Service product.ini hard-coded password (critical 9.3)
- [CVE-2024-34200](https://insights.sbomify.com/CVE-2024-34200/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34219 and fix it if it is affected.

What it is: CVE-2024-34219 is a high-severity vulnerability in n/a, published on 9 May 2024. 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-2024-34219 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-2024-34219/ (Markdown: https://insights.sbomify.com/CVE-2024-34219/index.md)
```

## Sources

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

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