Skip to main content

Tapo C200 Firmware CVE-2025-8065

HIGH
Stack-based Buffer Overflow (CWE-121)
2025-12-20 f23511db-6c3e-4e32-a477-6aa17d310630
8.7
CVSS 4.0 · Vendor: f23511db-6c3e-4e32-a477-6aa17d310630
View

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

Real-world risk is moderate to high for deployed devices but exploitation complexity contains the threat. The CVSS 4.0 score of 8.7 reflects high confidentiality, integrity, and availability impact (VC:H/VI:H/VA:H) with attack vector limited to adjacent networks (AV:A), low attack complexity (AC:L), and no privileges required (PR:N). The adjacent network requirement means attackers must have local network access-either physical presence, compromised network credentials, or pivot from another compromised device-significantly reducing the attack surface compared to internet-exposed vulnerabilities. However, the lack of authentication requirements (PR:N) means any adjacent attacker can exploit without credentials once network access is achieved. No public exploit identified at time of analysis, and SSVC framework considerations show this affects consumer IoT devices where automated exploitation would have limited scope (single LAN segment). The primary risk scenarios involve targeted attacks against specific networks (corporate espionage, residential surveillance manipulation) or worm-like propagation within already-compromised networks. Compared to internet-facing RCE vulnerabilities, the adjacent-network constraint and consumer device context lower real-world urgency, though the complete device compromise and potential for persistent surveillance access elevate concern for privacy-sensitive deployments.

Exploit ScenarioDerived

An attacker who has gained access to the local network-either through compromised WiFi credentials, physical proximity to an unsecured wireless network, or lateral movement from another compromised device-identifies Tapo C200 or C520WS cameras via network scanning on ONVIF service ports (typically TCP 80/443/8000). The attacker crafts a malicious SOAP request containing an XML namespace prefix exceeding the parser's stack buffer size and sends it to the camera's ONVIF endpoint without requiring authentication. The oversized prefix triggers the buffer overflow during XML parsing, overwriting stack memory with attacker-controlled data including shellcode. Successful exploitation grants code execution with elevated privileges in the camera's firmware context, allowing the attacker to disable recording, manipulate video feeds, extract stored footage, establish persistent backdoor access, or pivot to attack other network-connected devices. No public exploit identified at time of analysis, though the detailed vulnerability description provides sufficient technical information for skilled attackers to develop working exploits.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 02, 2026

Stack-based buffer overflow in the ONVIF SOAP XML parser of TP-Link Tapo C200 v3 (firmware ≤1.4.1) and C520WS v2.6 cameras enables unauthenticated remote code execution from adjacent networks. Attackers can send crafted SOAP requests with oversized namespace prefixes to trigger memory corruption and achieve full device compromise with elevated privileges. EPSS probability and KEV status indicate no public exploit identified at time of analysis, though the vulnerability affects widely deployed consumer IoT cameras with network exposure.

RemediationAI

Users should immediately update to patched firmware versions available from TP-Link's official support portal. For Tapo C200 v3, download the latest firmware from https://www.tp-link.com/us/support/download/tapo-c200/v3/#Firmware-Release-Notes and for Tapo C520WS from https://www.tp-link.com/us/support/download/tapo-c520ws/#Firmware-Release-Notes. Apply updates through the Tapo mobile app or web management interface following vendor instructions at https://www.tp-link.com/us/support/faq/4849/. As a temporary mitigation until patching, isolate affected cameras on a dedicated VLAN with strict firewall rules preventing lateral movement, disable ONVIF protocol support if not required for integration, and restrict camera network access to only trusted management systems. Organizations should audit which devices require ONVIF functionality and consider disabling it entirely on cameras used solely with the Tapo native app. Network segmentation is critical given the adjacent-network attack vector-ensure IoT cameras cannot reach or be reached from corporate workstation networks.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability (CWE-121: Stack-based Buffer Overflow) resides in the ONVIF SOAP XML parser implementation used by TP-Link Tapo security cameras. ONVIF is an industry-standard protocol for IP camera interoperability, using SOAP-based web services for device management and control. The parser fails to validate the length of XML namespace prefixes before copying them into fixed-size stack buffers during tag processing. When a maliciously crafted SOAP message contains an oversized namespace prefix, the unbounded copy operation overflows the stack buffer, corrupting adjacent memory regions. This memory corruption can be leveraged to overwrite return addresses or function pointers, enabling arbitrary code execution in the context of the camera's firmware process. Affected products per CPE data include TP-Link Tapo C200 firmware versions 1.3.3 through 1.4.1 (builds 230228 through 241212) running on Tapo C200 v3 hardware, indicating over 10 firmware releases spanning nearly two years contain this flaw. The vulnerability is exploitable through the camera's ONVIF service interface, typically exposed on the local network for integration with video management systems and smart home platforms.

Know when Tapo C200 Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (f23511db-6c3e-4e32-a477-6aa17d310630) PRIMARY 8.7 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (f23511db-6c3e-4e32-a477-6aa17d310630) · only source for this CVE.

CVSS VectorVendor: f23511db-6c3e-4e32-a477-6aa17d310630

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A stack-based buffer overflow vulnerability was identified in the ONVIF SOAP XML Parser in Tapo C200 v3 and C520WS v2.6. When processing XML tags with namespace prefixes, the parser fails to validate the prefix length before copying it to a fixed-size stack buffer. It allowed a crafted SOAP request with an oversized namespace prefix to cause memory corruption in stack.

An unauthenticated attacker on the same local network may exploit this flaw to enable remote code execution with elevated privileges, leading to full compromise of the device.

Executive ViewAI

Why It Matters

TP-Link Tapo C200 and C520WS cameras contain a critical unauthenticated remote code execution vulnerability in their SOAP XML parser that allows attackers on adjacent networks to fully compromise devices without credentials. This poses significant risk to organizations deploying these cameras for surveillance, as compromised devices can serve as network entry points or be weaponized for lateral movement, with no vendor patch currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Implement network segmentation-isolate cameras on a dedicated IoT VLAN with egress filtering to prevent lateral movement; (2) Disable UPnP and remote access features via camera configuration; (3) Block inbound SOAP/HTTP requests (ports 80, 443, 8080, 8443) from untrusted networks at perimeter firewalls; (4) Monitor camera network traffic for anomalous SOAP requests with oversized XML payloads; (5) Consider replacing affected models with devices from vendors with active security support. These controls reduce but do not eliminate risk-patch or hardware replacement is required for complete remediation.

Threat Intelligence Overview

EPSS Score
0.0%
Top 94% exploitable
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)CVE.org

cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.3:build_230228:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.4:build_230424:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.5:build_230717:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.7:build_230920:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.9:build_231019:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.11:build_231115:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.13:build_240327:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.14:build_240513:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.3.15:build_240715:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.4.1:build_241212:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.4.2:build_250313:*:*:*:*:*:*
cpe:2.3:o:tp-link:tapo_c200_firmware:1.4.4:build_250922:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy