An error in Windows 10 causes blue screen and crashes your operating system, simply by running a certain 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 Appliances of Windows, they can pass a Win3 device names path2, as an argument in various Windows programming functions. For example, this allows an application to interact directly with a physical disk without going through the file system.
Lykkegaard discovered the following path, for 'console multiplexer driver' which he believes is used for 'kernel / usermode ipc'. When you run this route in various ways, even by low-privileged users, it is triggered vacation Windows 10 operating system.
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.
Although it is not specified whether this error could be exploited for remote code execution or to gain additional privileges, in its current form it could be used as a denial of service attack.
In a real-world scenario, this bug could be exploited by malicious elements who have access to a network and want to cover their tracks while duration 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.