An especially “nasty” Windows 10 bug can potentially corrupt your hard drive simply by looking in a folder. It can be prevented by the normal ways of not opening email attachments or using any external drives that you do not trust.

Previously this week, security scientists found a bug in Windows 10 that will corrupt the tough drive by merely opening a folder, clicking a faster way, or by other relatively innocuous ways.

The vulnerability can be from another location activated if having any sort of service permitting file opens of specific names to occur.
Its embeddable in HTML, sharred folders etc.
Until now only repercussion have actually been running chkdsk on boot- and now the MFT have corrupted

— Jonas L (@jonasLyk) January 9, 2021

CERT/CC vulnerability analyst Will Dormann later on confirmed the bug and added that it had several vectors aside from opening a folder or file faster way, including opening an ISO, VHD, or VHDX, extracting a Zip file, opening an HTML file without a MoTW, and others. It can be particularly wicked if the code is embedded in the faster way to a genuine application.

Upon activating, the bug will automatically corrupt the NTFS MFT (master file table). Often Windows will right away turn up a notice to reboot your computer system so it can run a drive repair. Nevertheless, Dormann states this is not constantly the case, and in some cases users will need to run a manual repair.

It should fix the damage successfully. At least as soon as I got this screen, which required manual intervention to do the repair work. pic.twitter.com/0fvYUDLEz5

— Will Dormann (@wdormann) January 15, 2021

Microsoft understands about the problem and told The Verge it was working on a repair. In the meantime, it urges users to be careful and practice correct cyber health.

” We are aware of this problem and will supply an upgrade in a future release. Using this technique depends on social engineering and as always we encourage our clients to practice good computing practices online, consisting of working out care when opening unidentified files, or accepting file transfers.”

Dormann remains downhearted about a repair coming from Microsoft, claiming that he reported a similar NTFS bug two years ago that still is not repaired. He stated he would not divulge the special file name that causes the corruption for now.

LEAVE A REPLY

Please enter your comment!
Please enter your name here