Security News > 2021 > January > Google Chrome blocks 7 more ports to stop NAT Slipstreaming attacks
Google Chrome now blocks access to websites on an additional seven TCP ports to protect against the NAT Slipstreaming 2.0 vulnerability.
When the vulnerability was first disclosed, Google stated that they would block HTTP and HTTPS access to TCP ports 5060 and 5061 to protect against this vulnerability in the release of Chrome 87.
Today, Google announced that Chrome would also block HTTP, HTTPS, and FTP access to 69, 137, 161, 1719, 1720, 1723, and 6566 TCP ports.
"The NAT Slipstream 2.0 attack is a kind of cross-protocol request forgery which permits malicious internet servers to attack computers on a private network behind a NAT device. The attack depends on being able to send traffic on port 1720.".
"To prevent future attacks, this change also blocks several other ports which are known to be inspected by NAT devices and may be subject to similar exploitation," Google explains in the feature description on their Chrome Platform Status site.
While Edge will likely use the same ports as Chrome, it is not known what ports were blocked in Safari and Firefox.
News URL
Related news
- Google Chrome will let you send money to your favourite website (source)
- Google fixes ninth Chrome zero-day exploited in attacks this year (source)
- Google Chrome gets a mind of its own for some security fixes (source)
- Google Chrome Switches to ML-KEM for Post-Quantum Cryptography Defense (source)
- New Google Chrome feature will translate complex pages in real time (source)
- New Octo Android malware version impersonates NordVPN, Google Chrome (source)
- Google fixes Android kernel zero-day exploited in targeted attacks (source)
- 18-year-old security flaw in Firefox and Chrome exploited in attacks (source)
- Google raps Iran's APT42 for raining down spear-phishing attacks (source)
- Google to Remove App that Made Google Pixel Devices Vulnerable to Attacks (source)