A new Windows 10 bug causes a single link blue screen


Windows 10 security vulnerabilities have become, along with minor system glitches, already commonplace for users. And it is that to the recent reports of the critical error that could damage our hard drive just by seeing the icon of a file or writing a simple command, now another slightly similar problem is added that leads to the well-known blue screen of death.

As shared by Bleeping Computer, this new error simply involves a URL or link to an internal Windows location (which we have preferred to avoid sharing for obvious reasons) and you don't even need to click on it to activate it. The mere fact that Windows 10 tries to process this path, such as when it is entered in the address bar of a browser, will be enough to block our system.

The report says it could be remotely exploited by tricking users into downloading a URL file from Windows. The operating system will try to generate an icon from that data, which will cause the system to crash. In some cases, it could even be exploited to cause an immediate blue screen when logging into Windows. In this way, the end result for users could vary from a simple verification to being stuck in an automatic repair cycle during system startup.

In fact, as shared by Jonas Lykkegaard, the Windows security researcher who discovered the bug, low- privileged Windows users have access to connect to this path, making it easy for any common program run from the computer to crash Windows 10.

Luckily, this bug focuses on a basic component of human interaction, requiring users to type (voluntarily or unintentionally) some command or URL, or simply click on an unknown link or icon. For this reason, once again, we call for safe browsing: whenever we come across these types of suspicious elements, it is best to avoid them and look for information about them.

For its part, Microsoft has already stated that it has opened an investigation into this error, although at the moment no resolution has been published.

Post a Comment

0 Comments