News for hackers. Stuff that matters.
Re:DDoS Letter to Chairman Wheeler by bogomipz on Friday October 28, 2016 @08:12PM (#12821826)
Sure but UPNP just opens up the outbound connection no?

A command and control connection for a botnet would still need an inbound NAT rule as would the ability to get the IoT device on the LAN in the first place compromise it right? Or am I missing something?

Re:DDoS Letter to Chairman Wheeler by wmf on Friday October 28, 2016 @08:33PM (#12821922)
NATs allow outbound connections by default; UPnP opens up incoming connections.
Re:DDoS Letter to Chairman Wheeler by bogomipz on Friday October 28, 2016 @09:16PM (#12822076)
Oh I see the UPnP IGP AddPortMapping. Do the Merkai access that UPnP profile out of the box?
Re:DDoS Letter to Chairman Wheeler by fryguy on Friday October 28, 2016 @09:18PM (#12822087)
My understanding of UPNP is that it allows the router itself to become a discover-able device on the network. Then the IoT device connects to the router and adds a static port mapping from the router's public IP address on a specific port to the IoT's private IP address. The NAT still works as it normally does where any packets that try to leave the network get remapped by the router seamlessly. The danger in this case is the IoT device has a listening port on your public IP address, allowing attackers to connect directly to it through your router.