Cyber Resilience

CVE-2023-35717

Auth Bypass in Tp-Link Tapo C210 Firmware 1.3.0

Published
03 May 2024
Modified
12 August 2025
CVSS Score v3 8.8
Click a component to see what it means
Raw vectorCVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0062 47th percentile
Risk Priority 65 floored blend · peak EPSS

Summary

CVE-2023-35717 is a high-severity Weak Password Recovery Mechanism for Forgotten Password (CWE-640) vulnerability in Tp-Link Tapo C210 Firmware. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

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

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

TP-Link Tapo C210 Password Recovery Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of TP-Link Tapo C210 IP cameras. Authentication is not required to exploit this vulnerability. The specific flaw exists within the password…

more

recovery mechanism. The issue results from reliance upon the secrecy of the password derivation algorithm when generating a recovery password. An attacker can leverage this vulnerability to bypass authentication on the system. . Was ZDI-CAN-20484.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-41184Same product: Tp-Link Tapo C210
CVE-2026-9609Shared CWE-640
CVE-2026-15155Shared CWE-640
CVE-2026-37106Shared CWE-640
CVE-2026-24467Shared CWE-640
CVE-2023-46138Shared CWE-640
CVE-2025-6216Shared CWE-640
CVE-2024-12295Shared CWE-640
CVE-2026-9466Shared CWE-640
CVE-2026-4136Shared CWE-640

Affected Assets

tp-link
tapo c210 firmware
1.3.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V7.4.3

Mitigating Controls (NIST 800-53 r5) AI

Identity proofing at appropriate assurance levels ensures forgotten-password recovery cannot succeed without strong verification of the user.

Authenticator management requires secure distribution, reset, and verification procedures that directly address weak password recovery flows.

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 mostly match
prevents

Credential lifecycle management directly includes password reset/recovery flows.

PR.AA-02 mostly match
prevents

Identity proofing is the core control that prevents weak or bypassed recovery mechanisms.

PR.AA-03 partial match
prevents

Authentication policy covers strength/MFA but does not address recovery path weaknesses.

PR.PS-06 partial match
prevents

Secure SDLC reduces implementation flaws but is not specific to password-recovery design.

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.

degrades

Strong authentication-information lifecycle rules directly address weak password-recovery flows.

prevents

Secure-SDLC practices can embed strong recovery design, yet the control is broader than this single weakness.

prevents

Application-security requirements can mandate secure recovery flows, but the control covers many other requirements.

prevents

Secure-coding standards can prevent weak recovery implementations, yet the control is wider in scope.

mitigates

Secure-authentication requirements include robust forgotten-password procedures.

none

Proper access-rights provisioning can limit who can trigger recovery, but does not fix the recovery mechanism itself.

References