Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain admin credentials via reuse or phishing
-
DeliveryGain access to device LAN segment
-
ExploitAuthenticate to ONVIF service with admin account
-
InstallCraft SOAP CreateUsers request with excessive XML user nodes
-
C2Send request to ONVIF endpoint
-
ExecuteStack buffer overflow triggers service crash
-
ImpactONVIF management DoS condition
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. |
| Exploitation Conditions | Three concrete prerequisites must all be satisfied: (1) Adjacent network access - the attacker must be on the same LAN or network segment as the camera (AV:A); internet-based exploitation is not possible without a prior foothold on the local network. (2) High-privilege authentication - the CVSS vector specifies PR:H, meaning the attacker must authenticate to the camera with administrator-level credentials before issuing the ONVIF CreateUsers request; unauthenticated exploitation is not possible. (3) ONVIF service enabled and reachable - the ONVIF management service must be running and accessible on the device, which is standard for this camera model but can be disabled. Limiting factors that reduce realistic risk: the adjacent-only vector eliminates all internet-sourced attacks; the admin credential requirement means an attacker without prior access to camera management cannot weaponize this vulnerability; and the impact is confined to a DoS of the ONVIF service only - no code execution, data exfiltration, or persistent device compromise has been described. |
| Impact | The CVSS 4.0 score of 6.8 reflects a meaningful but constrained risk profile. The vector AV:A/AC:L/AT:N/PR:H/UI:N breaks down as follows: attack vector is adjacent (LAN segment only - not internet-reachable without prior foothold), complexity is low, and no additional attack requirements exist, but high privileges (PR:H) are mandatory, meaning the attacker must already hold administrator-level credentials on the camera. The impact is limited entirely to availability (VA:H) with zero confidentiality or integrity impact (VC:N/VI:N). No EPSS score was provided in available intelligence, so exploitation probability cannot be quantified. The absence of a KEV listing and no identified public POC further suggests this is not currently being exploited at scale. Real-world risk is low-to-moderate: the combination of adjacent-only access and required admin credentials substantially narrows the realistic attacker population to insiders, compromised LAN actors, or those who have separately acquired admin credentials. The primary operational risk is service disruption to ONVIF-dependent NVR/VMS integrations rather than data breach or device takeover. |
| Exploit ScenarioDerived | An attacker who has obtained administrator-level credentials to the Tapo C520WS v2 - whether through credential reuse, phishing, or a prior network compromise - connects from the same LAN segment and sends a crafted ONVIF CreateUsers SOAP request containing hundreds of XML user node entries. The camera's ONVIF service processes the malformed request without validating the node count, overflows a fixed-size stack buffer, and the process crashes, taking down ONVIF management functions until the device is rebooted or the service restarts. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 06, 2026
Stack-based buffer overflow in the ONVIF CreateUsers service of the TP-Link Tapo C520WS v2 IP camera allows an authenticated, adjacent-network attacker to crash the ONVIF management process by sending a crafted request with an excessive number of XML user nodes. Exploitation results in a denial-of-service condition that disrupts ONVIF-based device configuration and management until the service recovers or the device is rebooted. No public exploit code or CISA KEV listing has been identified at time of analysis; the vendor (TP-Link) has released a firmware patch.
RemediationAI
Apply the latest Tapo C520WS v2 firmware update from the TP-Link official download page (https://www.tp-link.com/us/support/download/tapo-c520ws/#Firmware-Release-Notes or https://www.tp-link.com/en/support/download/tapo-c520ws/#Firmware-Release-Notes) and review the vendor security advisory at https://www.tp-link.com/us/support/faq/5120/ for exact patched version details; the specific fixed firmware build number was not present in available intelligence and must be confirmed against the release notes before deployment. As a compensating control prior to patching, isolate the camera on a dedicated IoT VLAN with firewall rules preventing cross-segment ONVIF access, which eliminates the adjacent-network exposure (AV:A) and fully mitigates remote exploitation at the cost of potentially disrupting cross-VLAN NVR/VMS integrations. If ONVIF functionality is not required for your deployment, disabling the ONVIF service entirely removes the attack surface with no impact on basic camera operation but will break third-party ONVIF-compatible management tools. Additionally, audit and minimize the number of accounts with high-privilege access to the device, as PR:H is a hard prerequisite for exploitation.
Affected VersionsENISA
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
The TP-Link Tapo C520WS v2 is a consumer-grade outdoor IP camera that implements the ONVIF (Open Network Video Interface Forum) protocol for standardized management interoperability, including the CreateUsers service for provisioning camera accounts via XML-formatted SOAP requests. CWE-121 (Stack-Based Buffer Overflow) identifies the root cause class: the firmware allocates a fixed-size stack buffer to hold parsed XML user node data from the ONVIF CreateUsers request body, but fails to bound-check the number of user entries supplied. Submitting an excessive node count overflows the stack frame, corrupting return addresses or local state and causing the ONVIF service process to terminate. This pattern - insufficient XML input validation in embedded network-facing services - is a recurring weakness in IoT/camera firmware, typically arising from constrained development environments without stack canaries or bounds-checking libraries. The affected CPE is cpe:2.3:a:tp-link_systems_inc.:tapo_c520ws_v2:*:*:*:*:*:*:*:*.
Know when Tapo C520Ws V2 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
CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Primary rating from Vendor (TPLink) · only source for this CVE.
CVSS VectorVendor: TPLink
Lifecycle Timeline
1DescriptionCVE.org
A stack‑based buffer overflow vulnerability exists in Tapo C520WS v2 in the ONVIF CreateUsers service, where the device fails to properly validate the number of XML user nodes during request processing. An authenticated attacker can send a specially crafted ONVIF request containing an excessive number of user entries to trigger memory corruption.
Successful exploitation may cause the ONVIF management service to terminate unexpectedly, resulting in a denial‑of‑service (DoS) condition that disrupts device configuration and management functions.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
More in Tapo C520Ws V2
View allDenial of service in the RTSP server of TP-Link Tapo C520WS v2 IP cameras allows adjacent network attackers to render th
Authorization bypass in TP-Link Tapo C520WS v2 cameras allows holders of restricted accounts (such as hub users) to exec
Format string injection in the TP-Link Tapo C520WS v2 ONVIF Subscribe service allows a high-privileged attacker on the s
Format string exploitation in TP-Link's Tapo C520WS v2 ONVIF management service allows an authenticated attacker on an a
Stack-based buffer overflow in TP-Link Tapo C520WS v2 allows an authenticated attacker with adjacent network access to c
EUVD-2026-34934
GHSA-cpjh-84vm-rvxf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB