Google Chrome is not allowing HTTP, FTP, and HTTPS access to TCP port while preventing 10080 port that is causing the Slipstreaming 2.0 attacks. Last year the security researcher founded the updated version of the NAT Slipstreaming vulnerability that permits the attacks to overlaps the visitor’s NAT firewall while regaining access to other TCP or UDP ports that over the visitor’s internal network.
These vulnerabilities may permit the attackers to execute a wide range of attacks that also deals with manipulating the router configurations while gaining the access to the private network services. Although these vulnerabilities will work on several specific ports that were monitored by the routers application-level Gateway (ALG) and now the developer of the Google Chore is blocking these vulnerable ports to prevent these unwanted vulnerabilities and reduce the traffic.

What Actions Taken by The Google?
However, Google Chrome is now blocking the HTTP, HTTPS, and FTP port on 69, 137, 161, 554, 1719, 1723, 1720, 5060, 5061, and 6566. Google also stated blocking the TCP port 10080 in Chrome, which was already blocked by Firefox in November.
The experts also said that blocking the port is a good option and the browser developer also aimed that the application named Amanda Backup tool and VMWare vCenter also uses these port will be affected by this decision.
Whereas, the most important point is the blocking of port 10080 is that some other developer may use it as another option to port 80. The Google developers also said that it is an attractive port for HTTP because it termites with 80 and it didn’t need to use the root permissions while executing on Unix System.
Meanwhile, the organization Rice will going to update some privacy policies that the developers will override while using the port.
Once, the port is blocked the users are seeing an error message that was displaying at “ERR_UNSAFE_PORT” while opening the port.

In case you want to access the website that runs on the same port then you may use a different post that is not blocked by the Google Chrome