4 ms·
Vulnerable by default? If a device is listening to UPnP on the WAN interface, the fault is not on UPnP but on whoever configured it to be open on the WAN. IMO,
by Kikawala 9y ago
Vulnerable by default?
If a device is listening to UPnP on the WAN interface, the fault is not on UPnP but on whoever configured it to be open on the WAN. IMO, all of these zeroconf protocols should be limited to responding back only to the local segment and not allowed to traverse gateways.
- jacquesm 9y agoOne of the documented use cases for UPnP is IGD which expressly allows UPnP devices to configure fire wall rules and to set up NAT to map ports to the outside world. So a UPnP device that wishes to expose itself to the outside world is able to do so and this is by design, not by accident. Whether you agree with that or not is another matter.
- MichaelGG 9y agoThat doesn't mean the upnp listener needs to listen on the WAN interface.
- CountSessine 9y agoAgreed - but can there ever be any legitimate use case for an home router to speak IGD over its WAN interface? IGD is typically meant to allow your Xbox on your LAN to set up forwarding rules.
- duskwuff 9y agoNone. Exposing miniupnpd on a public interface is always a misconfiguration. I'm disappointed that the application even allows it -- it has to know which one is public to set up IP forwarding rules, so it has no excuse.
- voltagex_ 9y agoWhat about not replying to unicast responses? Or rate limiting by default?
- azinman2 9y agoWhen is it ever ok for UPnP to work across the internet? That’s not what it’s meant for.
- okwap 9y agoTR-064 is based on UPnP/SSDP, for example.