CVE-2025-14299
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe HTTPS server on Tapo C200 V3 IP cameras fails to properly validate the Content-Length HTTP header, allowing an integer overflow when processing malformed headers. An unauthenticated attacker on the same local network segment can send crafted HTTPS requests with specially crafted Content-Length values, triggering excessive memory allocation that crashes the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.3.3= 1.3.4= 1.3.5= 1.3.7= 1.3.9= 1.3.11= 1.3.13= 1.3.14= 1.3.15= 1.4.1= 1.4.2= 1.4.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Tapo C200Access the camera's web interface or mobile app, or check the device label/sticker to verify the exact model number is TP-Link Tapo C200.Affected if Device model is not Tapo C200, then this CVE does not apply.
-
Check installed firmware versionLog into the Tapo C200 web interface or mobile app and navigate to Settings > Device Info > Firmware Version, or use the Tapo app to view device details.Affected if Firmware version matches any of these: 1.3.3, 1.3.4, 1.3.5, 1.3.7, 1.3.9, 1.3.11, 1.3.13, 1.3.14, 1.3.15, 1.4.1, 1.4.2, 1.4.4. If your version is not in this list, you are likely not affected.
-
Verify HTTPS server is enabledIn the Tapo C200 web interface, go to Settings > Network > HTTPS Settings, or check the camera's HTTP/HTTPS server configuration via the mobile app.Affected if HTTPS server is enabled on the device. The vulnerability exists in the HTTPS server component, so if HTTPS is disabled, the attack surface may be reduced.
-
Assess network accessibilityDetermine whether the Tapo C200 camera is on a network segment shared with untrusted devices, or if it is isolated on a dedicated VLAN or firewalled network.Affected if The camera is reachable by unauthenticated attackers on the same local network segment. If the device is fully isolated from untrusted local users, exploitation is less likely.
You are likely affected if you have a Tapo C200 camera running one of the listed firmware versions, with HTTPS enabled, and the device is accessible to unauthenticated users on your local network segment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware patch when available; until then, isolate affected devices on a restricted network segment to limit exposure to local attackers, or consider replacing with a supported device model.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14299 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14299 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data