Cyber Resilience

CVE-2024-34219

Exposed Creds in Totolink Cp450 Firmware 4.1.0cu.747_b20191224

Public PoCExposed Creds
Published
14 May 2024
Modified
04 April 2025
CVSS Score v3.1 8.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
EPSS Score 0.21 97th percentile
Risk Priority 77 floored blend · peak EPSS

Summary

CVE-2024-34219 is a high-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Totolink Cp450 Firmware. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1078.001 Default Accounts Stealth
Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-7332Same product: Totolink Cp450
CVE-2024-34211Same product: Totolink Cp450
CVE-2024-7465Same product: Totolink Cp450
CVE-2024-34205Same product: Totolink Cp450
CVE-2024-34203Same product: Totolink Cp450
CVE-2024-8162Same vendor: Totolink
CVE-2024-34212Same product: Totolink Cp450
CVE-2024-34210Same product: Totolink Cp450
CVE-2024-34217Same product: Totolink Cp450
CVE-2023-24147Same vendor: Totolink

Affected Assets

totolink
cp450 firmware
4.1.0cu.747_b20191224

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Authenticator management requires secure distribution and handling of credentials, structurally discouraging hard-coded values.

Cryptographic key management mandates proper establishment and handling instead of embedding keys in code.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-01 partial match
prevents

PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.

PR.AA-02 none match
prevents

PR.AA-02 addresses human identity proofing and per-person credential issuance at enrollment; it has no bearing on whether developers embed static credentials in software.

PR.DS-01 none match
prevents

PR.DS-01 addresses encryption and integrity of stored data but never touches credential or key management practices, so it neither prevents hard-coded credentials nor removes any of their risk.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Education on secure configuration practices discourages technical staff from embedding or relying on hard-coded credentials in systems and applications.

mitigates

Secure key-generation, distribution and storage procedures reduce the likelihood that hard-coded or default cryptographic keys will be introduced or left unprotected.

prevents

Explicit prohibition of hard-coded passwords and unauthenticated external services stops credentials from being embedded directly in source code.

prevents

Contractual requirements for secure coding practices and evidence of testing make it less likely that hard-coded credentials will be introduced or remain undetected in delivered code.

none

Requiring independent oversight and timely disabling of non-human identities makes it harder for hard-coded or long-lived credentials to remain exploitable.

none

Mandating immediate replacement of vendor-supplied default credentials eliminates the use of hard-coded or factory passwords that attackers can trivially obtain from documentation or firmware.

References