Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14299: CWE-770 Allocation of Resources Without Limits or Throttling in TP-Link Systems Inc. Tapo C200 V3

0
High
VulnerabilityCVE-2025-14299cvecve-2025-14299cwe-770
Published: Sat Dec 20 2025 (12/20/2025, 00:42:43 UTC)
Source: CVE Database V5
Vendor/Project: TP-Link Systems Inc.
Product: Tapo C200 V3

Description

CVE-2025-14299 is a high-severity vulnerability affecting the TP-Link Tapo C200 V3 camera. The device's HTTPS server improperly validates the Content-Length header, leading to an integer overflow that causes excessive memory allocation. An unauthenticated attacker on the same local network can exploit this flaw by sending crafted HTTPS requests, resulting in a denial-of-service (DoS) condition due to device crash. No user interaction or authentication is required, and the attack vector is local network access. Although no exploits are currently known in the wild, the vulnerability poses a significant risk to device availability. The CVSS 4. 0 score is 7. 1, reflecting high severity. European organizations using these cameras should prioritize mitigation to prevent potential service disruptions. Mitigations include network segmentation, limiting local network access, and monitoring for anomalous HTTPS traffic.

AI-Powered Analysis

AILast updated: 12/20/2025, 01:37:18 UTC

Technical Analysis

CVE-2025-14299 is a vulnerability in the TP-Link Tapo C200 V3 smart camera's HTTPS server implementation. The root cause is improper validation of the Content-Length HTTP header, which can lead to an integer overflow when processing incoming HTTPS requests. This overflow causes the device to allocate excessive amounts of memory without limits or throttling, a classic example of CWE-770 (Allocation of Resources Without Limits or Throttling). An attacker who is unauthenticated but positioned on the same local network segment as the device can exploit this flaw by sending specially crafted HTTPS requests with manipulated Content-Length headers. The resulting excessive memory allocation overwhelms the device's resources, causing it to crash and become unavailable, effectively creating a denial-of-service (DoS) condition. The vulnerability does not require any user interaction or prior authentication, making it easier to exploit in environments where the attacker has local network access. The CVSS 4.0 vector indicates the attack requires local network access (AV:A), has low attack complexity (AC:L), no privileges or user interaction, and results in high impact on availability (VA:H). No known exploits have been reported in the wild yet, and no patches are currently linked, indicating that affected users should be vigilant and apply mitigations proactively. This vulnerability underscores the risks inherent in IoT devices that lack robust input validation and resource management controls, particularly in consumer-grade smart home equipment.

Potential Impact

For European organizations, the impact of CVE-2025-14299 primarily involves availability disruption of Tapo C200 V3 cameras. These devices are often used for security monitoring, remote surveillance, and operational oversight in both residential and small business environments. A successful DoS attack could disable camera feeds, leading to blind spots in security coverage and potential safety risks. In critical infrastructure or sensitive environments where these cameras are deployed, such outages could hinder incident response or surveillance capabilities. The requirement for local network access limits remote exploitation but does not eliminate risk, especially in environments with weak network segmentation or compromised internal networks. Additionally, the denial-of-service could be leveraged as part of a broader attack chain to distract or disable security monitoring. The lack of authentication requirement increases the threat from insider attackers or malicious actors who gain local network access through other means. Given the widespread use of TP-Link devices in Europe, particularly in small and medium enterprises and smart homes, the disruption potential is significant. Organizations relying on these devices should consider the operational impact of camera downtime and the potential for attackers to exploit this vulnerability to degrade security posture.

Mitigation Recommendations

1. Network Segmentation: Isolate IoT devices like the Tapo C200 V3 on separate VLANs or subnets with strict access controls to prevent unauthorized local network access. 2. Access Control: Restrict local network access to trusted devices only, using MAC filtering, 802.1X authentication, or network access control (NAC) solutions. 3. Monitor Network Traffic: Deploy network monitoring tools to detect anomalous HTTPS requests or unusual spikes in traffic targeting IoT devices, especially malformed Content-Length headers. 4. Device Hardening: Disable unnecessary services and interfaces on the camera to reduce attack surface. 5. Firmware Updates: Regularly check for and apply firmware updates from TP-Link once patches become available for this vulnerability. 6. Incident Response Planning: Prepare for potential DoS incidents by having backup monitoring solutions or failover cameras to maintain surveillance continuity. 7. Vendor Engagement: Engage with TP-Link support channels to obtain timelines for patches and request security advisories. 8. User Awareness: Educate users and administrators about the risks of local network attacks and the importance of securing Wi-Fi and wired networks against unauthorized access. These measures go beyond generic advice by focusing on network architecture, traffic analysis, and operational readiness specific to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
TPLink
Date Reserved
2025-12-08T22:05:00.941Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6945fa2fc376abdb7e67a371

Added to database: 12/20/2025, 1:21:51 AM

Last enriched: 12/20/2025, 1:37:18 AM

Last updated: 12/20/2025, 4:05:04 AM

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats