Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Bug Windows Microsoft

Code Published for Triggering a BSOD on Windows Computers -- Even If They're Locked (bleepingcomputer.com) 118

"A Romanian hardware expert has published proof-of-concept code on GitHub that will crash most Windows computers within seconds, even if the computer is in a locked state," writes BleepingComputer. An anonymous reader quotes their report: The code exploits a vulnerability in Microsoft's handling of NTFS filesystem images and was discovered by Marius Tivadar, a security researcher with Bitdefender. The expert's proof-of-concept code contains a malformed NTFS image that users can take and place on a USB thumb drive. Inserting this USB thumb drive in a Windows computer crashes the system within seconds, resulting in a Blue Screen of Death (BSOD). "Auto-play is activated by default," Tivadar wrote in a PDF document detailing the bug and its impact...

Tivadar contacted Microsoft about the issue in July 2017, but published the PoC code today after the OS maker declined to classify the issue as a security bug. Microsoft downgraded the bug's severity because exploiting it requires either physical access or social engineering (tricking the user).

This discussion has been archived. No new comments can be posted.

Code Published for Triggering a BSOD on Windows Computers -- Even If They're Locked

Comments Filter:
  • Topsy turvy (Score:1, Troll)

    by arth1 ( 260657 )

    Wake me up when someone publishes something that's guaranteed not to crash Windows...

  • USB (Score:2, Informative)

    by amiga3D ( 567632 )

    USB is problematic anyway. Where I worked if you inserted a flash drive into a computer it would lock you out and send an alert to security. Good way to get fired.

    • Pff what a joke. Where I worked if you inserted a flash drive into your computer they sent in Droidekas to exterminate everyone in the room.
  • by Anonymous Coward

    I've found another similar exploit.

    If you pull on the flexible plastic tube that link the computer to the wall, the computer will abruptly shutdown without warning. Sometimes, you may even *corrupt* the file system, if you time it right! And Microsoft refuses to acknowledge this as a severe vulnerability! Crazy!

  • by AndyKron ( 937105 ) on Saturday April 28, 2018 @04:55PM (#56520921)
    That's strange. My computer always asks me what I want to do when I put a USB drive in, and I never changed the default.
    • by Anonymous Coward

      Well, go ahead and build this USB image and plug it in

      Windows will ask you something, alright: whether IRQL is not less or equal

    • I'll bet it does that after it mounts it.
    • Notice that it asks you what you want to do while looking at the files and proposing things such as opening the pictures on it?

      This isn't about auto-play, it's about auto-mount, something that every desktop OS does.

  • Just tried it (Score:5, Interesting)

    by TheDarkener ( 198348 ) on Saturday April 28, 2018 @05:05PM (#56520975) Homepage

    Doesn't work, at least on a (since Jan 2018) unpatched Win7 Home Premium system. "The file or directory is corrupt and unreadable" when trying to access the drive even. Maybe I have to patch it?

    • Note that it was x86 Windows install, not sure if that has anything to do with it.

    • by Anonymous Coward

      It was already patched via an update... Without credit to Tivadar.

  • by Anonymous Coward

    even if the computer is in a locked state

    I feel this bug won't be fixed by M$ because this is a very important feature for authorities. This is an intentional feature so TLA can just stick-in their USB toolkit and unlock any machines at will at checkpoints and airports.

    Sorry, this is a secret feature and NOT A BUG.

  • Well it is a way quick to turn off a Windows PC

    Well makes for a great system lock

    Well at least the screen looks scary, with that on the PC at Starbucks, no one will steal the laptop

    I will be here all week, tip the waitresses

  • Transcript of Internet Caucus Panel Discussion. [techlawjournal.com] Re: Administration's new encryption policy.
    Date: September 28, 1999.
    Weldon statement. [techlawjournal.com]

    Rep. Curt Weldon : Thank you. Let me see if I can liven things up here in the last couple of minutes of the luncheon. First of all, I apologize for being late. And I thank Bob and the members of the caucus for inviting me here.

    ...

    But the point is that when John Hamre briefed me, and gave me the three key points of this change, there are a lot of unanswered questions. He

  • Hmm, interesting... In 2013 a Windows kernel developer expressed his opinion about NTFS source code.

    Oh god, the NTFS code is a purple opium-fueled Victorian horror novel that uses global recursive locks and SEH for flow control. Let's write ReFs instead. (And hey, let's start by copying and pasting the NTFS source code and removing half the features! Then let's add checksums, because checksums are cool, right, and now with checksums we're just as good as ZFS? Right? And who needs quotas anyway?)

    The full ar [zorinaq.com]

  • What is the point ? If I have physical access to the machine I can induce the equivalent of a BSOD by unplugging the fsck'n thing. Why bother with a USB stick to make it crash ? Seems like an exercise in stupidity. I've discovered that I can crash your computer even if locked if I can get physical access to it by picking it up off the shelf and throwing it to the floor. Rinse, repeat....

    • What is the point ? If I have physical access to the machine I can induce the equivalent of a BSOD by unplugging the fsck'n thing. Why bother with a USB stick to make it crash ? Seems like an exercise in stupidity. I've discovered that I can crash your computer even if locked if I can get physical access to it by picking it up off the shelf and throwing it to the floor. Rinse, repeat....

      I think if you thought about it a while, you might find that if you wanted to do some damage, that thumb drive might allow you to walk in, plug in, BSOD, and walk out without destroying anything at the scene of the crime. Think about it.

      I notice you didn't have a similar "This is no problem" for the social engineering aspect.

      I know that it is fashionable to believe that Windows has no problems, but seems like it's taking denial these days to exonerate the Perfect OS.

      • by Archfeld ( 6757 )

        Wouldn't unplugging the machine do the same thing ? I can't think of ANY OS that doesn't have 'problems', and I've worked on more than my fair share, from DOS/VSE, to OS/360, to VM/XA,, TMDS, OS/2, Windows, Unix, Linux, Solaris, and many others, classified as programming languages and/or OS's. The so called 'social engineering' aspect is beyond the hacking aspect. You can educate the ignorant, but stupid is forever, besides how do you socially engineer someone to put a USB stick with some code into a machin

        • Wouldn't unplugging the machine do the same thing ?

          Oh hell, let's just call it a Windows feature.

        • by hoggoth ( 414195 )

          > how do you socially engineer someone to put a USB stick with some code into a machine

          "Hi, I'm here for an interview. Oh shoot I spilled coffee on my resume. Could you please print a copy for me? It's on this thumbdrive."

          • by Archfeld ( 6757 )

            There would be another available opening if anyone mounted a USB stick of any sort, let alone one brought on site by non employee. I've been to places that have USB ports disabled or had local mice plugged in and had locked covers over the input to prevent adding anything. But I generally don't work for very small offices so I guess that kind of stuff must still occur.

      • Worth adding that a crash can often be turned into an exploit with a little work..
    • by suutar ( 1860506 )

      unplugging the computer doesn't lead to buffer overflow exploits. Breaking the kernel can (though this one doesn't seem to yet).

  • Microsoft downgraded the bug's severity because exploiting it requires either physical access or social engineering (tricking the user).

    So physical access and social engineering aren't problems now?

    • Microsoft downgraded the bug's severity because exploiting it requires either physical access or social engineering (tricking the user).

      So physical access and social engineering aren't problems now?

      Theft and idiocy are not things that can be fixed with software updates.

      • Microsoft downgraded the bug's severity because exploiting it requires either physical access or social engineering (tricking the user).

        So physical access and social engineering aren't problems now?

        Theft and idiocy are not things that can be fixed with software updates.

        Go onto a college campus, or perhaps a library. Computers everywhere. Or a Doctors office. I understand perhaps your idea of computer security might be armed guards with orders to terminate with extreme prejudice anyone that gets with in a ten meter kill zone of the computer - but hey, if you are willing to accept the idea that your computer can be BSOD'd with a simple geek stick, then call it a feature. Much damage can be done that does not require your break the computer sens of how things are done.

    • If you find an USB stick somewhere - aren't you curious about the content?

      • If you find an USB stick somewhere - aren't you curious about the content?

        I used to keep a sacrificial Windows machine around for the very purpose of plugging in suspect CDs and thumb drives.

        Pop 'em in, and see what happens.

        A lot of people don't realize how many of us have been exploited.

      • by hoggoth ( 414195 )

        Yes I am curious. That's why I boot into a Linux Live-CD and make sure my hard drive is not mounted before I plug in the thumbdrive.

    • So physical access and social engineering aren't problems now?

      Not ones warranting rolling out fixes to prevent an otherwise secure computer from crashing and remaining secure.

    • by Dog-Cow ( 21281 )

      If you were literate, you'd know "downgraded" is not the same as "we're going to ignore it".

      • If you were literate, you'd know "downgraded" is not the same as "we're going to ignore it".

        Okay - when is the projected fix date? I've heard "downgraded" a lot over the years. It means very well we're going to ignore it.

        Otherwise, you hear "We'll work on it after all of the other problems are fixed." Or something. Since than never happens, it means "we'll ignore it."

        It also tells me that there are a whole lot of other really critical problems going on that require immediate and intensive work on successful ongoing exploits that are sucking up all of our time.

        Either that or "we're just go

        • Further, there's several errors in this article and misunderstanding by the researcher. Just look at the comments on bleeping computer, no one got the PoC to work.
    • What is hard for you to understand levels of severity? It's fucking explained right there. Are you not in ANY technical field where there's multiple levels of severity? Like holy fuck, that's some basic newbie type questioning. This is a fucking tech site.
      • What is hard for you to understand levels of severity? It's fucking explained right there. Are you not in ANY technical field where there's multiple levels of severity? Like holy fuck, that's some basic newbie type questioning. This is a fucking tech site.

        Sure there is various levels of severity. Would you bet 20 years of your life that this is not and will not be a problem? You don't ignor vulnerabilities. Plus, your completely dismissive attitude about this makes you a security risk. You know how many of the security incidents happen? People just like you - If you worked for me, and went into that rant, you'd have an appointment with security waiting for you the second you left my office. You are not the genius you think you are.

"The vast majority of successful major crimes against property are perpetrated by individuals abusing positions of trust." -- Lawrence Dalzell

Working...