Google Chrome is the most used browser today and they are constantly looking for ways to improve important aspects such as security and privacy. Whenever a problem arises they try to find a solution so that it does not affect users or at least decrease the probability. In this article we echo how the Google browser is going to block another port, TCP 554 , to avoid NAT Slipstreaming attacks.
Chrome will block TCP port 554
It is not the first time that we have seen that Google Chrome blocks ports for this purpose. We have already seen that to improve security it has taken these types of measures. In this case, it is TCP port 554 and its mission is to avoid NAT Slipstreaming attacks that could compromise the security of users.
Keep in mind that hackers use the vulnerabilities and flaws they find to achieve their goal. NAT Slipstreaming 2.0 attacks are one more example. Now, to avoid reducing the impact, correcting that vulnerability, Chrome is going to close one more new port.
This new version of the NAT Slipstreaming vulnerability would allow possible malicious scripts to bypass the NAT firewall when a visitor enters a web page and thus access any TCP / UDP port on the visitor’s internal network.
However, this vulnerability only works on specific ports that are monitored by the application-level gateway of a router. This means that browsers, such as Google Chrome, have blocked certain vulnerable ports that do not receive much traffic.
As we mentioned, Chrome has previously blocked some ports , such as TCP 5060 and 5061. Most recently, last January, it decided to block seven more ports. Now it is the turn of TCP port 554.
Blocking ports can be a problem for visitors
We must bear in mind that the fact of blocking ports by browsers could also affect users. After all, when entering a website that uses that port, there could be a blockage and the impossibility of navigating normally.
If a user tries to enter a website that uses a blocked port, the message ERR_UNSAFE_PORT will appear. Therefore, those responsible for web pages that host their site in one of these blocked ports should change it to a different port and thus allow visitors to navigate normally.
On the other hand, the developers of Google and Safari are also raising blocking access to port 10080, which Firefox already blocks, but they are hesitant due to legitimate requests from the web browser to that port. Therefore, it is likely that TCP port 554 is not the last to be blocked in Chrome and we will soon have at least one more port.
Maintaining safety when browsing is essential. It is something that depends both on the browser itself and on the user, on the measures taken when entering the Internet, such as using antivirus or keeping the equipment updated. Enabling DNS in Chrome, for example, helps to navigate more securely.
Ultimately, Google Chrome has decided to block TCP port 554. It may not be the last, since in a short time they could block at least one more. As always, the goal is to improve security and make browsing more reliable.