<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Tapo C320WS (V2.0, &lt;= 1.5.3 Build 260304) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/tapo-c320ws-v2.0--1.5.3-build-260304/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 20 Oct 2026 18:42:16 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/tapo-c320ws-v2.0--1.5.3-build-260304/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>TP-Link Tapo C320WS: Stack-based buffer overflow RCE (CVE-2026-105810)</title><link>https://feed.craftedsignal.io/briefs/2026-10-tplink-tapo-c320ws-rce/</link><pubDate>Tue, 20 Oct 2026 18:42:16 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-tplink-tapo-c320ws-rce/</guid><description>An authenticated stack-based buffer overflow in the TP-Link Tapo C320WS camera allows remote code execution as root via the Wi-Fi onboarding process.</description><content:encoded><![CDATA[<p>CVE-2026-105810 is a high-severity, authenticated stack-based buffer overflow vulnerability affecting the TP-Link Tapo C320WS camera (hardware V2.0, firmware ≤ 1.5.3 Build 260304). The vulnerability resides in the <code>onboarding.connect</code> (<code>connectAp</code>) handler, which incorrectly calculates the destination capacity when base64-decoding a user-supplied Wi-Fi password. By providing an overly long, crafted password string, an authenticated administrative user on the adjacent network can overflow a fixed 1024-byte stack buffer. Because the vulnerable binary is a non-PIE ARM executable lacking stack canaries, an attacker can reliably execute arbitrary code as root by redirecting execution flow via a ROP chain to call <code>system()</code>. A functional proof-of-concept exploit is publicly available, necessitating immediate patching to firmware <code>1.6.6 Build 260917 Rel.81089n</code> or later.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains administrative authentication to the target TP-Link Tapo C320WS local API.</li>
<li>Attacker interacts with the <code>onboarding.connect</code> (<code>connectAp</code>) handler via the device local management interface.</li>
<li>Attacker submits a specially crafted, base64-encoded Wi-Fi password string exceeding 1024 bytes.</li>
<li>The device decoder incorrectly determines buffer capacity, leading to memory corruption.</li>
<li>The stack-based buffer overflow overwrites the function return address on the stack.</li>
<li>The corrupted return address redirects the processor to an attacker-controlled ROP chain.</li>
<li>The ROP chain executes <code>system()</code> to run arbitrary commands on the underlying device.</li>
<li>Attacker gains full root command execution capabilities on the camera.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in full remote command execution as the root user on the camera. This provides attackers with total control over the device, allowing them to intercept surveillance feeds, pivot into the local network, or use the camera as a foothold for further malicious activity. This vulnerability affects TP-Link Tapo C320WS cameras running firmware version 1.5.3 Build 260304 or earlier.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch all TP-Link Tapo C320WS cameras to firmware version <code>1.6.6 Build 260917 Rel.81089n</code> or later immediately.</li>
<li>Implement network segmentation for IoT devices to restrict access to the camera's management API (TCP/443) to authorized administrative workstations only.</li>
<li>Audit administrative account passwords and ensure strong credentials are used to prevent unauthorized access to the vulnerable API endpoints.</li>
<li>Monitor network traffic originating from IoT segments for unexpected command execution patterns or ROP chain remnants if advanced network inspection is available.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2026-105810</category><category>rce</category><category>iot-security</category></item></channel></rss>