{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-14299 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14299 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14299 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C200 V3, published on 20 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14299 and fix it if it is affected.\n\nWhat it is: CVE-2025-14299 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C200 V3, published on 20 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-14299 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Tapo C200 V3. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-14299/ (Markdown: https://insights.sbomify.com/CVE-2025-14299/index.md)","id":"CVE-2025-14299","markdown":"https://insights.sbomify.com/CVE-2025-14299/index.md","name":"CVE-2025-14299","record":{"aliases":["GHSA-7cw2-wjj4-46p6"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tapo C200 camera","requires_auth":"none","summary":"An unauthenticated attacker on the local network can cause a denial of service on the Tapo C200 camera via integer overflow in HTTPS Content-Length validation.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"tapo_c200_firmware","vendor":"tp-link"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Improper Content-Length Validation in HTTPS Requests on Tapo C200","id":"CVE-2025-14299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Unauthenticated Access to connectAP API Endpoint on Tapo C100, C200 \u0026 C425","id":"CVE-2025-14300"},"packages":[],"prev":{"headline":"Cross-site scripting in FiboSearch – Ajax Search for WooCommerce","id":"CVE-2025-14298"},"products":["Tapo C200 V3"],"published":"2025-12-20","related":[{"cvss_score":9.8,"headline":"TP-LINK Tapo C200 remote code execution vulnerability","id":"CVE-2021-4045","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.7,"headline":"Unauthenticated Access to connectAP API Endpoint on Tapo C100, C200 \u0026 C425","id":"CVE-2025-14300","kev_date_added":null,"published":"2025-12-20"},{"cvss_score":8.7,"headline":"Remote Code Execution via Stack-based Buffer Overflow in ONVIF SOAP Parser in TP-Link Tapo C200 and C520WS","id":"CVE-2025-8065","kev_date_added":null,"published":"2025-12-20"},{"cvss_score":7.1,"headline":"Denial-of-Service via Oversized Encrypted Credential Input in TP-Link Tapo C200","id":"CVE-2026-15316","kev_date_added":null,"published":"2026-08-18"},{"cvss_score":7.1,"headline":"Denial-of-Service Vulnerability via Malformed IPv4 Fragmentation Handling in TP-Link Tapo C200","id":"CVE-2026-12760","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":7.1,"headline":"Authenticated Stack-based Buffer Overflow in RTSP Authentication of Tapo C200","id":"CVE-2026-1871","kev_date_added":null,"published":"2026-06-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-22","vendors":["TP-Link Systems Inc."]},"summary":"An unauthenticated attacker on the local network can cause a denial of service on the Tapo C200 camera via integer overflow in HTTPS Content-Length validation.","url":"https://insights.sbomify.com/CVE-2025-14299/"}