Slashdot Mirror


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

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.

49 of 105 comments (clear)

  1. Break out my Windows 3.11 box by jfdavis668 · · Score: 1

    16 bit software will save the day again.

    1. Re: Break out my Windows 3.11 box by jfdavis668 · · Score: 1

      Ok, I have a copy of Windows 2.11 around here somewhere. Not sure if that counted as being released.

    2. Re: Break out my Windows 3.11 box by jfdavis668 · · Score: 1

      Then I can play Reversi to my heart's content.

    3. Re: Break out my Windows 3.11 box by BronsCon · · Score: 2

      More reliable sources say 95 and on, which makes sense as prior versions didn't ship with a network stack.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    4. Re: Break out my Windows 3.11 box by Anonymous Coward · · Score: 1

      Kind of hard when that version doesn't have an IP stack.

    5. Re: Break out my Windows 3.11 box by werewolf1031 · · Score: 1

      Maybe I'm just old and senile, but didn't 3.11, ie. "Windows for Workgroups", include one?

    6. Re: Break out my Windows 3.11 box by BronsCon · · Score: 1

      Ah, I stand corrected, as I forgot about WFW.

      However, it appears that WFW gained NetBIOS support via NWNBLink, which provided support for NetBIOS over IPX/SPX, rather than ICP/IP. That is, it would not have been vulnerable to BadTunnel.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    7. Re: Break out my Windows 3.11 box by flyingfsck · · Score: 1

      Well apart from having to dig up the books on IPX/SPX, the tunnel would likely work over that too. When MS creates a network backdoor for the NSA, they are very thorough...

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    8. Re: Break out my Windows 3.11 box by BronsCon · · Score: 4, Informative

      At worst, it could have been exploited by a system on the same LAN, as IPX/SPX was very frame-size and frame-order dependent, rendering it effectively useless as a WAN protocol.

      Additionally, read up on how the vulnerability functions. I had to read up on it a bit more than I already had in order to write this reply, but here's a summary: The attack involved convincing a Windows machine, via a flaw in NetBIOS over TCP/IP, that the attacking machine is a valid WPAD or ISATAP server. ISATAP is an IPv6 transition mechanism so we can rule that out as a WFW attack vector. WPAD hadn't been created by Netscap yet in 1993 when WFW was released (it was developed in 1996 as part of Netscape Navigator 2.0), so that's ruled out as well.

      Looks like WFW was safe.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    9. Re: Break out my Windows 3.11 box by wierd_w · · Score: 1

      WFW used NETBEUI, and IPX, yes.

      It did have a TCP/IP implementation though. It just didnt do netbios over it.

      win3.1 needed trumpet tcp, or some other 3rd party stack, but WFW had it natively. This was the era where Netscape was really starting to hit the scene, and the web was an emerging phenomenon. IIRC, there was an early version of IE for WFW.

      That is why when win95 rolled out, with IE preinstalled (but not thuroughly baked in), it started MS's ascendency. When win98 hit with it permanently baked in, it started the lawsuit.

      History lesson over, netbios over tcp debuted on win9x. Prior to that, it was NETBEUI and IPX.

    10. Re: Break out my Windows 3.11 box by BronsCon · · Score: 2
      For the sake of those who will only read up to the quoted line:

      It did have a TCP/IP implementation though. It just didnt do netbios over it.

      This is correct; and BadTunnel is initiated via an exploit in NetBIOS over IPX/SPX and relies on one of two additional services for which WFW had no support.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    11. Re: Break out my Windows 3.11 box by BronsCon · · Score: 1
      GAH!! I meant:

      BadTunnel is initiated via an exploit in NetBIOS over TCP/IP

      Proofread.
      Every.
      Post.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    12. Re: Break out my Windows 3.11 box by sconeu · · Score: 1

      Piker. I am going to install my copy of Windows 1.03. As soon as I can find a 5.25" 360K drive.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    13. Re: Break out my Windows 3.11 box by drolli · · Score: 1

      Yay! I'll filter everthing which is not IPX in the router!

    14. Re: Break out my Windows 3.11 box by Maritz · · Score: 1

      I don't even think the first win95 had TCP/IP stack. What did they call it, winsock? I think they rolled it out in a service pack. I realise I could just google this, but I don't care enough.

      --
      I do not want your cheap brainburning drugs. They are useless for work. And I am a working man today.
    15. Re: Break out my Windows 3.11 box by DarkOx · · Score: 1

      Microsoft did provide a tcp driver for wfw3.11 as an add on.

      I

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    16. Re: Break out my Windows 3.11 box by DaveMikulec · · Score: 1

      Amateur. My copy's on datasette.

      --
      "Shall we play a game?" -W.O.P.R.
    17. Re: Break out my Windows 3.11 box by Bob+the+Super+Hamste · · Score: 1

      I think I still have one in my basement. It probably still works given how damn near indestructible those things were.

      --
      Time to offend someone
    18. Re: Break out my Windows 3.11 box by BronsCon · · Score: 1

      They actually released the Windows TCP/IP stack in 3.11a or b, I forget which. NetBIOS didn't use it until Win95, though.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    19. Re: Break out my Windows 3.11 box by BronsCon · · Score: 1

      Yes, but NetBIOS didn't gain the ability to use it until Win95 and WFW never supported WPAD or ISATAP, one or the other of which was required, in conjunction with NetBIOS over TCP/IP, in order to exploit the flaw.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    20. Re: Break out my Windows 3.11 box by BronsCon · · Score: 1

      Did they support WPAD and/or ISATAP?

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
  2. Re:WinXP Patch? by phrostie · · Score: 5, Funny

    just upgrade to Win 10 and everything will be ok.
    let go of your old OS and let MS set you free.

    for a limited time only.

  3. Re: WinXP Patch? by Anonymous Coward · · Score: 1

    I wonder if this had been known and maybe even disclosed by Microsoft to the NSA, especially since it's all known windows versions.

  4. All versions of Windows, ever released? by evilviper · · Score: 1

    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.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    1. Re:All versions of Windows, ever released? by msauve · · Score: 1

      "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?

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    2. Re:All versions of Windows, ever released? by evilviper · · Score: 2

      Nope.

      in August 1994, Microsoft released an add-on package (codenamed Wolverine) that provided TCP/IP support in Windows for Workgroups 3.11. Wolverine was a 32-bit stack

      https://en.wikipedia.org/wiki/...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    3. Re:All versions of Windows, ever released? by MikeBabcock · · Score: 1

      Some of us remember installing Trumpet Winsock on Windows 3.1; it certainly was not DOS.

      --
      - Michael T. Babcock (Yes, I blog)
    4. Re:All versions of Windows, ever released? by flyingfsck · · Score: 1

      It's OK, Peter Tattam's Trumpet Winsock network stack will fix that little problem for you: http://www.trumpet.com.au/

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    5. Re:All versions of Windows, ever released? by drinkypoo · · Score: 1

      Some of us remember installing Trumpet Winsock on Windows 3.1; it certainly was not DOS.

      If you were very very lucky you had the TCP stack from TGV (Two guys and a vax) instead. They got bought by Cisco at the same time that Windows 95 came out with its own TCP stack, so they abandoned the main product and turned them into a cable modem development facility because Cisco.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:All versions of Windows, ever released? by DaveMikulec · · Score: 1

      Yup. Along with Spry Mosaic!

      --
      "Shall we play a game?" -W.O.P.R.
  5. Microsoft please stop this madness by WaffleMonster · · Score: 4, Insightful

    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.

    1. Re:Microsoft please stop this madness by Monoman · · Score: 2

      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/...
      https://technet.microsoft.com/...

      --
      Keep the Classic Slashdot.
    2. Re:Microsoft please stop this madness by skids · · Score: 1

      That... really depends on the distro. There are plenty of unnecessary discovery services distros can be tempted to install because they want their product to satisfy users who expect their OS to "see their printer" and such crap without being told to. All such services offer more potential code surface for network-borne attacks.

  6. So sorry by Dunbal · · Score: 2

    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.

    --
    Seven puppies were harmed during the making of this post.
    1. Re:So sorry by Nunya666 · · Score: 1

      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 gives Linux a fair shot first. Of course, he would have to pay for the Windoze licence, which should encourage him to give the free option (meaning Linux) an honest effort. Hopefully, I can create another Linux convert.

  7. Re:Told folks turn off NetBIOS since 1996 by Pikoro · · Score: 2

    I tend to use a philosophy of "less is more"

    That's why you have a multi megabyte host file right?

    Also. Bing? Really?

    --
    "Freedom in the USA is not the ability to do what you want. It is the ability to stop others from doing what THEY want"
  8. Re:WinXP Patch? by uncqual · · Score: 2

    Yes, and if you're interested in being approached for interesting jobs, once the LinkedIn acquisition is complete, Microsoft will probably punish anyone not running Windows 10 by burying their names in search results. Get with the program - NOW!

    --
    Why is there an "insightful" mod and why isn't it "-1"? If I wanted insight, I wouldn't be reading /.
  9. Nothing to do with VNC protocol by scdeimos · · Score: 1

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

  10. Natively by Anonymous Coward · · Score: 1

    firewalls are natively designed to open the port

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

  11. Re:Now I wonder if I saw this in action? by ShaunC · · Score: 2

    Do some Googling for the make and model of your modem, and of the router if it's a separate piece of equipment. There are exploits going around for some CPE, cable modems in particular, that allow a remote attacker to change the configured name servers among other things. If rebooting the modem or router fixed the problem, it's more likely that's what was compromised, not a NetBIOS tunnel in Windows.

    --
    Thanks to the War on Drugs, it's easier to buy meth than it is to buy cold medicine!
  12. Re:WinXP Patch? by donaldm · · Score: 1

    just upgrade to Win 10 and everything will be ok. let go of your old OS and let MS set you free.

    for a limited time only.

    Why would I want to install Windows 10 when my perfectly good Fedora 23 distro works perfectly?

    If I want to install Malware then Microsoft Windows 10 would be the way to go, after all, take a look at what Windows 10 is doing to get people to "upgrade" and what settings are on by default. Sure you can turn most of these settings to "off" but even after hacking the Registry, which most people can't do, are you quite sure you really have turned everything off?

    Of course, we all really know that Big Brother^H^H^H^H^H^H^H^H^H^H^H Microsoft has our best interests at heart.

    --
    There ain't no such thing as proprietary standards only proprietary formats. Standards are by definition open.
  13. Researcher doesn't understand firewalls by Anonymous Coward · · Score: 1

    "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.

  14. Can I patch my Win7 without "upgrading" to Win10? by KWTm · · Score: 1

    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 Windows 8, so if my Windows 7 installation ever craps out, I'll have to be dragged screaming and kicking back into the Windows 8+ world.

    As soon as I got wind of Microsoft's "We'll upgrade you to Win10 for free! Whether or not you like!" scam, I disabled Windows updates. Now I have to figure out whether I want to get Win7 updated to protect me from this vulnerability, and risk having the entire system turned into a Win10 system. :sigh:

    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  15. Re:WinXP Patch? by phrostie · · Score: 1

    it was a joke.

    I'm more of a debian guy myself, but fedora is good too.

  16. will never be patched by cellocgw · · Score: 1

    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.

    --
    https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
  17. NetBIOS should be disabled anyway by evolutionary · · Score: 1

    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.

    --
    "Imagination is more important than knowledge" - Einstein
  18. Re:Told folks turn off NetBIOS since 1996 by cellocgw · · Score: 1

    I tend to use a philosophy of "less is more"

    Actually, less is more than more.

    Just ask any csh jock.

    --
    https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
  19. Re:WinXP Patch? by Coren22 · · Score: 1

    Yeah, the next zero day to come along affecting XP will be a big deal since it is out of support and therefore the problem will never be patched. I totally agree that you are going to be more secure running Windows 7, 8, or 10 than XP.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  20. Re:WinXP Patch? by doccus · · Score: 1

    Yeah. but hey. c'mon now. Net Bios? Anyone still even *using* it? ;-)