1-minute read
What a defender needs to know
TP-Link TL-WR940N hardware revision 6 contains an unauthenticated remote-code-execution flaw in its RTSP connection-tracking kernel module. The fixed regional builds are V6_260528 for English and US devices and V6_260527 for Japan.
The attack does not start at the management page. A LAN client connects to an attacker-controlled RTSP server. A crafted reply travels back through that established session, and the router parses it in the kernel. The resulting stack buffer overflow can crash the router or permit code execution and full device compromise. TP-Link does not report active exploitation or provide a universal packet signature.
Inventory exact model, hardware revision, region, and running firmware. For revision 6, install firmware only from the matching regional TP-Link support route, then verify the running build in the device interface. Network restrictions on untrusted RTSP traffic are containment, not an equivalent fix.
The strongest incident check is correlation: find unexplained outbound RTSP sessions from LAN clients and line them up with router restarts, loss of forwarding, configuration changes, or new router-originated traffic. Preserve both directions of available packet captures. Port 554 by itself does not prove exploitation or clear a device.
After a suspicious failure, rebuild from trusted firmware, restore reviewed configuration, replace administrative credentials, and inspect the client that opened the session. Verify that every revision 6 unit reports the regional fixed build or has been retired. Investigate suspicious sessions and device behavior, and document missing telemetry as an evidence gap.