TP-Link Tapo C200 V3 HTTP Header Content-Length allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in TP-Link Tapo C200 V3. Affected is an unknown function of the component HTTP Header Handler. Performing a manipulation of the argument Content-Length results in allocation of resources. This vulnerability is reported as CVE-2025-14299. The attacker must have access to the local network to execute the attack. No exploit exists.
Details
A vulnerability was found in TP-Link Tapo C200 V3 (the affected version is unknown). It has been classified as critical. This affects an unknown code of the component HTTP Header Handler. The manipulation of the argument Content-Length with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:
The HTTPS server on Tapo C200 V3 does not properly validate the Content-Length header, which can lead to an integer overflow. An unauthenticated attacker on the same local network segment can send crafted HTTPS requests to trigger excessive memory allocation, causing the device to crash and resulting in denial-of-service (DoS).
The weakness was disclosed by Simone Margaritelli. The advisory is shared at tp-link.com. This vulnerability is uniquely identified as CVE-2025-14299 since 12/08/2025. The exploitability is told to be easy. The attack needs to be initiated within the local network. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-204620). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.tp-link.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.5
VulDB Temp Score: 6.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/08/2025 CVE reserved12/20/2025 Advisory disclosed
12/20/2025 VulDB entry created
01/09/2026 VulDB entry last update
Sources
Vendor: tp-link.comAdvisory: tp-link.com
Researcher: Simone Margaritelli
Status: Not defined
CVE: CVE-2025-14299 (🔒)
GCVE (CVE): GCVE-0-2025-14299
GCVE (VulDB): GCVE-100-337677
EUVD: 🔒
Entry
Created: 12/20/2025 08:50Updated: 01/09/2026 10:24
Changes: 12/20/2025 08:50 (65), 01/09/2026 06:18 (1), 01/09/2026 10:24 (9)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.