NAT Slipstream Attack 2.0

[upnorth]

Content source

https://www.theregister.com/2021/01/27/nat_slipstream_bypass/

The original NAT Slipstream potentially allowed a miscreant to access any TCP/UDP service tied to a victim's machine by bypassing the victim's NAT (Network Address Translation) and firewall defenses. It can be triggered via JavaScript code on a malicious website.

NAT Slipstream v2 takes the technique further by allowing a hacker to penetrate a vulnerable NAT/firewall and reach any internal IP on the network, rather than just the IP address of the victim's device. In other words, it may expose every connected thing on a targeted network – printers, video cameras, industrial control systems, and other unmanaged hardware – to the internet. Such devices, which generally lack security controls, may then be compromised and commandeered or otherwise abused.

The researchers disclosed their findings to the major browser vendors back in November 2020, and patches, consisting of port restrictions, have been deployed since then.

Knock, knock. Who's there? NAT. Nat who? A NAT URL-borne killer

Last year's slipstream technique revived to pierce vulnerable firewalls – browsers patched to thwart bypass attempts

www.theregister.com

 

[Andy Ful]

From the article:
"Seri and Vishnepolsky expressed doubt that these defenses will be the end of this particular attack vector. NATs, they say, were designed at a time when security was not a priority."

 

[ForgottenSeer 85179]

Google deploys Chrome mitigations against new NAT Slipstreaming attack

After the discovery of NAT Slipstreaming 2.0 attack this week, Google says it will block Chrome traffic on ports 69, 137, 161, 1719, 1720, 1723, 6566, and 10080.

www.zdnet.com

 

[Gandalf_The_Grey]

From the original article posted by @upnorth :

Chrome's fix arrived in v87.0.4280.141, on January 6, 2021. Microsoft Edge also deployed its fix, in v87.0.664.75, Apple released Safari v14.0.3 beta, with a stable channel release expected soon. And Mozilla's fixed up Firefox 85 arrived on Tuesday, January 26.

So, now from the big browsers only Safari is vulnerable, but hopefully not for long.