A bug in Windows 10 causes a blue screen and crashes your OS system, simply by running a specific path in a browser.
The security researcher Jonas Lykkegaard has repeatedly tweeted an unusual path that immediately crashes Windows 10 and displays a BSOD screen when you just run it in the Chrome address bar.
When developers want to interact directly with Windows devices, they can Win3 device names path2, as an argument to various Windows programming functions. For example, this allows an application to interact directly with a physical disk, without going through the system files.
Lykkegaard discovered the following path for the "console multiplexer driver” which it thinks is used for “kernel / usermode ipc”. Running this path in various ways, even by low-privileged users, causes Windows 10 to crash.
Try it in Chrome
\\. \ globalroot \ device \ condrv \ kernelconnect
CAUTION: You will lose all your jobs that you have not saved !!!
When connecting to this device, developers expect to communicate with it properly. Lykkegaard discovered that trying to connect to this path will throw an error Blue Screen of Death (BSOD) in Windows 10.
Worse, users with low Windows privileges can attempt to connect to the device using this path, making it easy for any program running on a computer to crash Windows 10.
In our tests, we confirmed this error in Windows 10 version 1709 and later. We could not try it in previous versions.
While it has not been determined whether this flaw could be exploited for remote code execution or to gain additional privileges, in its current form it can be used as attack denial of service.
In a real-world scenario, this error could be abused by malicious people who have access to a network and want to track it down during an attack.
If they have administrator credentials, they could remotely execute a command that has access to this path on all Windows 10 devices on a network to cause them to crash. Network damage could delay investigations or prevent controls from detecting an attack on a particular computer.
It does the same with Opera,
A small difference (I do not know why), is that in win x64 19042.746 he wants you to start him, while in win x86 19042.685 he reboots himself.