Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Bug Network Operating Systems Windows Communications Microsoft Networking Privacy Security Software The Internet News Build Technology

BadTunnel Bug Hijacks Network Traffic, Affects All Windows Versions (softpedia.com) 105

An anonymous reader writes: Microsoft has just patched a vulnerability that affects all Windows versions ever released. Called BadTunnel, the security flaw allows attackers to pass as a WAPD or ISATAP server and intercept all network traffic. Exploitation is trivial and firewalls are natively designed to open the port through which the attack is carried out. BadTunnel can be triggered whenever the user clicks URI or UNC links/paths in Office files, IE, Edge, or other applications that support the URI/VNC scheme (and most do). Additionally, an attacker can carry out his attack from the other side of the world, and does not need to have a foothold on the victim's network. While recent Windows OS versions received patches, exploitation points remain open for non-supported Windows operating systems such as XP, Windows Server 2003, and others. For these operating systems, and for those that can't be updated just yet, system administrators should disable NetBIOS.
This discussion has been archived. No new comments can be posted.

BadTunnel Bug Hijacks Network Traffic, Affects All Windows Versions

Comments Filter:
  • 16 bit software will save the day again.
  • Wow! And to think, Windows 1.0, 2.0 and 3.0 didn't have any networking support! Yet they somehow have bugs that allows diverting network traffic that they don't and can't generate!

    Windows 3.11 was the first to include networking, and I'm going to bet it wasn't affected, either.

    • by msauve ( 701917 )
      "Microsoft has just patched a vulnerability that affects all Windows versions ever released."

      But fortunately, according to the summary, they still patched all versions. Where do I get the patch for XP?
    • It's OK, Peter Tattam's Trumpet Winsock network stack will fix that little problem for you: http://www.trumpet.com.au/ [trumpet.com.au]
  • by WaffleMonster ( 969671 ) on Wednesday June 15, 2016 @07:48PM (#52326161)

    For the life of me I can't figure out why all of these tunneling/transition protocols are enabled by default in Windows. Who uses automatic IPv6 transition schemes in 2016? They certainly are not now nor have they ever been sufficiently reliable for production use and TTL for IPv6 amateur hour has long since expired. Why is this worth the massive security headaches these things invite?

    Have a script that I run on any new windows boxes. Part of it does the following.

    netsh interface teredo set state disabled
    netsh interface isatap set state disabled
    netsh interface 6to4 set state disabled

    I'm honestly perplexed and dumbfounded why Microsoft is (still) doing this.

    • by Monoman ( 8745 )

      IIRC it all started with Windows 7/Server 2008and some features that *required* IPV6. You didn't really have to be running IPv6 running on your network because MS was enabling tunneling and IPv6 by default so things would work automagically.

      https://en.wikipedia.org/wiki/... [wikipedia.org]
      https://technet.microsoft.com/... [microsoft.com]

  • by Dunbal ( 464142 ) * on Wednesday June 15, 2016 @08:12PM (#52326263)
    I'm sorry but I'm done with Microsoft patches. If hackers want to watch me play CS:GO or post on slashdot they're welcome to do it, but I won't risk Microsoft's definite installation of spyware.
    • I'm sorry but I'm done with Microsoft patches. If hackers want to watch me play CS:GO or post on slashdot they're welcome to do it, but I won't risk Microsoft's definite installation of spyware.

      On my own laptops, I agree completely. Unfortunately, my day job requires Microcrap Windoze.

      Even though my wife is not computer savvy and is a little resistant to change, her next laptop will get Windoze wiped from it and replaced with some version of Linux.

      I am currently configuring a second-hand laptop for a young family friend who is starting college this fall. It will have Linux on it, not Windoze. I warned him that he has to give Linux a try for two weeks. I will only install Windoze on it if he

    • Agree! I am trying to decide whether to allow Windows Update on my precious Windows 7 laptop which I finally bought for work after having been subject to Windows 8 crap (I'm trying to avoid the freshly-crapped Windows 10 with which one co-worker was saddled). Never thought I'd ever actually type the sequence of characters "precious Windows" in my lifetime, but after a lot of looking, I found a laptop Dell was selling that still had Windows 7 (Dell Vostro); it comes with a "Recovery CD-ROM" that installs W

  • I'm assuming that's a typo in the summary, that "URI/VNC" should read "URI/UNC".
  • by Anonymous Coward

    firewalls are natively designed to open the port

    My firewalls don't open any ports without me saying so.

  • by Anonymous Coward

    "Firewalls won't stop the attack, because UDP is a connectionless protocol. We are using it to establish a tunnel. That is why it be named 'BadTunnel'," Yu explains.

    My border firewall certainly stops this attack from outside the network since it does not allow IP protocol 41 which is used by ISATAP.

    Submitter doesn't understand firewalls either:

    firewalls are natively designed to open the port through which the attack is carried out

    That's may be true of the built-in Windows firewall, but it is not generally true for other ("real") firewalls.

  • Given how many "stealth Win10 install" patches are lined up in all our "windows updates" notifications, and that plenty of people on /. and elsewhere have stated clearly they've just plain shut down all updates rather than try to weed out the crapware ones, it's pretty clear this vulnerability will remain on plenty of machines for a long time.

  • NetBIOS was always a bit of a hack anyway. We shouldn't be using it anymore, period. An internal DNS is enough and easy to setup.

To stay youthful, stay useful.

Working...