Желілік порттарды бейнелеу протоколы және UPnP қауіпсіздігі

Network protocol for mapping ports

Internet Gateway Device (UPnP IGD) Control Protocol is a protocol based on UPnP for mapping ports in network address translation (NAT) setups, supported by some NAT enabled routers. It is a common communications protocol for automatically configuring port forwarding, and is part of an ISO/IEC Standard rather than an Internet Engineering Task Force standard.

UPnP IGDv2, published in 2010, added IPv6 support and corrected the misconception of an infinite lease time with a value of 0. The specifications are backward compatible, but there are compatibility issues e. g. with the Microsoft client.

There are numerous compatibility issues due the different interpretations of the very large actually backward compatible IGDv1 and IGDv2 specifications. One of them is the UPnP IGD client integrated with current Microsoft Windows and Xbox systems with certified IGDv2 routers. The compatibility issue still exist since the introduced of the IGDv1 client in Windows XP in 2001, and a IGDv2 router without a workaround that makes router port mapping impossible. If UPnP is only used to control router port mappings and pinholes, there are alternative, newer much simpler and lightweight protocols such as the PCP and the NAT PMP, both of which have been standardized as RFCs by the IETF. These alternatives are not yet known to have compatibility issues between different clients and servers, but adoption is still low. For consumer routers, only AVM and the open source router software projects OpenWrt, OPNsense, and pfSense are currently known to support PCP as an alternative to UPnP. AVM's Fritz!Box UPnP IGDv2 and PCP implementation has been very buggy since its introduction. In many cases it does not work.

Malware can exploit the IGD protocol to bring connected devices under the control of a foreign user. The Conficker worm is an example of a botnet created using this vector.