Windows 8.1 Can Be Crash By a Simple File Naming Bug

By Prempal Singh 0 Comment May 30, 2017  activator windows 8.1, asus, download windows 8.1, free download windows 8.1, hp, install windows 8.1, microsoft, microsoft windows 8.1, torrent windows 8.1, upgrade windows 8.1, win 8.1, windows 10, windows 7 download, windows 8 download, windows 8 to 8.1, windows 8.1 descargar, windows 8.1 iso, windows 8.1 key, windows 8.1 pro, windows 8.1 product key, windows phone, windows phone 8.1, windows update, windows update 8.1, ypdate to windows 8.1

In a blast from the past, a European researcher has uncovered an easy bug in the NTFS file system that constantly crashed Windows Vista to 8. 1 PCs.

Like the notorious Windows 95/98 /con/con bug, by entering a record name with “$MFT” the file-system bug locks up Windows best case situation or dumps it into a “blue screen of death” at worse.

$MFT is Windows NTFS’s Expert File Table. This special file tracks all documents on the volume, their logical location in directories, their physical location on hard, and file metadata.

Nevertheless, Windows is deceived into trying to start it as a regular record with the NtfsFindStartingNode function, the function can’t find it. Windows search for it again starting with the root file-system, in line with the researcher.

This time, throughout the NtfsOpenSubdirectory function, opens the file in a directory, but, on the next iteration of the loop, Windows detects that the file is not a directory, and so interrupts the job with a mistake.

Windows will then try to close access down to the file with NtfsTeardownStructures. This fails because to close the file, it had to open the file system when mounting. Windows will lock up while looping again and again.

Essentially this means if you try to use $MFT as part of a directory site name — for illustration, C: \$MFT\foo — the system crashes. The net impact is access to freeze out $MFT “captured forever” and the computer is locked up until it’s rebooted.

The most common way to exploit this bug get users to utilize a web browser to open a web page, with a fatal filename within it. For example, a web address requesting for an image record named C: \$MFT\Bummer. would start the crash.

The Chrome internet browser, however, will block this kind of strike because it won’t insert images with distorted directory paths.

Unfortunately, Internet Browser and Firefox will allow PCs to try and load such files and can suffer for it.

There are two bits of good information here. The foremost is that Windows 10 is immune to this attack. The other — and this is a mixed blessing — is can only it crash systems. You can’t make use of it — yet anyway — to deliver ransomware or other malware to a Windows system as it the case with WannaCry.

There is no area for this problem at the time.

Source: www.zdnet.com