Router vulnerability note - Tenda
Tenda AC6 V5: rebooting a router by sending it headers
What happened
TP-Link, Netgear and Tenda all have a version of this bug class, and here it is: the HTTP header parsing of the AC6 V5's admin interface mishandles a specially crafted series of requests, and the device reboots. The attacker sends multiple packets; nothing needs to be guessed and nobody needs to authenticate.
Zero-touch denial of service is the kind of finding that never appears in a spreadsheet as a disaster and appears in a support diary as "internet down again". A reboot on an access point costs thirty seconds. A reboot on the only router in a shop, during the card terminal's daily settlement, costs an afternoon of arguing.
Who is affected
Tenda AC6 V5.0 on V02.03.01.110; the exposure depends on who can reach the admin interface.
Check it yourself
Version, and who can reach the interface
UI: System settings > Firmware # from another machine on the LAN: $ curl -s -I http://192.168.0.1/ | head -2 $ ab -n 200 -c 20 http://192.168.0.1/ # a noisy guest does not crash it, but try # then from the WAN side, once, to see whether the page answers at all
Do this
- Update to a firmware newer than V02.03.01.110.
- Keep the management interface off the WAN, permanently, on any plastic-router-class device.
- If the unit reboots on its own, look at uptime before you look at the ISP.
- Consider a device with a real firmware support history for anything that carries payments.
How we handle it
For a customer on this class of hardware our standing advice is to buy predictability rather than features: a EUR 99 monitored router is expensive, a EUR 45 visit at midnight is not, and an unexplained reboot is what makes people buy the first one.