Gigabyte Radeon RX 6700 XT Gaming OC review
Corsair K70 RGB TKL keyboard review
Corsair RM650x (2021) power supply review
be quiet! Silent Loop 2 280mm review
Corsair K55 RGB PRO XT keyboard review
Guru3D Rig of the Month - March 2021
Intel Core i9-11900K processor review
Intel Core i5-11600K processor review
ASUS ROG Maximus XIII HERO review
MSI MEG Z590 ACE review
Critical NTFS bug in Windows 10 can corrupt HDD/SSD filesystem
Let me start off by declaring, DO NOT try to replicate/attempt what we write here in this article as it's very dangerous. A new vulnerability in Windows 10 has been detected, in specific if you have an NTFS formatted HDD/SSD.
And yes, NTFS if what pretty much everybody uses in Windows 10. Explained in its most simple essence the bug envokes triggering the filesystem/volume on a storage unit (NTFS formatted) to become corrupt. All you need to do is type one command line, and you can do so with limited privileges meaning you do not need to be an admin. And that by itself makes this a big vulnerability. Do NOT try this yourself! You have been warned:
Running this one command line causes hard drive errors that immediately corrupt the file system. The user is thereby forced to restart the computer to repair the damaged file system. The issue was found by infosec researcher Jonas L. A disk can be corrupted simply by accessing the $ i30 NTFS attribute in a folder. The command line shown below the precise example command that can damage the file system of a disk. The Windows ntfs index attribute, or $ i30 string, is associated with a directory that contains a list of files and subfolders of a folder. In some cases, the ntfs index may also contain deleted files and folders, which can be useful for sending the problem report to Microsoft. It is unclear why access to this attribute damages the disk, Jonas betokens that a registry key that would help diagnose the problem is not working. After running the command in Windows 10 command prompt and pressing Enter, the user will see an error message saying "The file or folder is corrupt and cannot be read." Windows 10 will immediately start displaying notifications asking the user to restart their PC and recover the damaged disk volume. On reboot, disk check is performed to repair the hard disk, reports Dutch website Hardware Info, who's source was securitynewspaper.
The vulnerability was discovered around the Windows 10 April 2018 update and has not been resolved to this day. according to a spokesperson for Microsoft, a solution is being worked on as soon as possible.
Rumor: Microsoft might share information on extremely critical vulnerability later today - 01/14/2020 03:53 PM
It's tagged as a rumor, but you can rest assured it'll become a fact. Keep an eye out on your Tuesday patches, and apply them. According to Krebs On Security, Microsoft is about to release an extre...
Critical Vulnerabilities in VLC Media Player Spotted and Patched - 06/27/2019 08:18 AM
VideoLAN has addressed a critical double-free vulnerability in the VLC media player that could allow an attacker to execute arbitrary code on target systems. This security loophole can be used to pla...
More than HP printer models vulnerable to two very critical vulnerabilities - 08/07/2018 08:31 AM
Over a hundred HP inkjet printers are vulnerable to remote code execution vulnerabilities that are classified by HP as critical. By exploiting the vulnerabilities, an attacker could remotely execut...
Eight new Spectre Variant Vulnerabilities for Intel Discovered - four of them critical - 05/03/2018 10:55 AM
News has just started spreading that researchers have sighted another eight Spectre like vulnerabilities in Intel processors, all resemble Spectre, four of them are critical. The new vulnerabilities ...
Adobe Warns About Critical Flash Zero-Day Bug - 04/13/2011 10:30 AM
A critical vulnerability exists in Flash Player 10.2.153.1 and earlier versions (Adobe Flash Player 10.2.154.25 and earlier for Chrome users) for Windows, Macintosh, Linux and Solaris, Adobe Flash Pla...
Ghosty
Senior Member
Posts: 5740
Joined: 2003-07-23
Senior Member
Posts: 5740
Joined: 2003-07-23
#5877867 Posted on: 01/15/2021 03:17 PM
Is FAT32 even an option anymore?
*NTFS
Is FAT32 even an option anymore?
Astyanax
Senior Member
Posts: 10059
Joined: 2018-03-21
Senior Member
Posts: 10059
Joined: 2018-03-21
#5877869 Posted on: 01/15/2021 03:20 PM
i'll try it later on my windows 8 vm.
I wonder if this traverses back to previous OS versions, they specifically mention 10 only.
i'll try it later on my windows 8 vm.
David3k
Senior Member
Posts: 107
Joined: 2003-07-29
Senior Member
Posts: 107
Joined: 2003-07-29
#5877870 Posted on: 01/15/2021 03:29 PM
HOLY CRAP, this actually explains a big issue I've been having for a while on my program on any of my computers; the program indexes only file and folder STATES on various marked locations over time at two minute intervals on NTFS filesystems.
A few weeks ago I added NTFS attributes on the list of metadata it probes for and records that information. It caused no immediate problems so I had a hard time tracking this down when I started getting issues week ago, since I've made a few more versions since then with other features and bugfixes.
I just updated the program to now exclude the $i30 attribute (NTFS bitmaps are already excluded) and hopefully I won't be seeing random NTFS errors crop up anymore.
Thanks for picking up on this, Hilbert, you've just solved a massive ongoing headache for me.
Twenty years, and you're still helping me out. : )
PS: I think I'm just going to exclude most NTFS attribute flags by default and only query the compressed and encrypted flags
HOLY CRAP, this actually explains a big issue I've been having for a while on my program on any of my computers; the program indexes only file and folder STATES on various marked locations over time at two minute intervals on NTFS filesystems.
A few weeks ago I added NTFS attributes on the list of metadata it probes for and records that information. It caused no immediate problems so I had a hard time tracking this down when I started getting issues week ago, since I've made a few more versions since then with other features and bugfixes.
I just updated the program to now exclude the $i30 attribute (NTFS bitmaps are already excluded) and hopefully I won't be seeing random NTFS errors crop up anymore.
Thanks for picking up on this, Hilbert, you've just solved a massive ongoing headache for me.
Twenty years, and you're still helping me out. : )
PS: I think I'm just going to exclude most NTFS attribute flags by default and only query the compressed and encrypted flags
alanm
Senior Member
Posts: 10090
Joined: 2004-05-10
Senior Member
Posts: 10090
Joined: 2004-05-10
#5877890 Posted on: 01/15/2021 04:40 PM
"The vulnerability was discovered around the Windows 10 April 2018 update and has not been resolved to this day. according to a spokesperson for Microsoft, a solution is being worked on as soon as possible."
"The vulnerability was discovered around the Windows 10 April 2018 update and has not been resolved to this day. according to a spokesperson for Microsoft, a solution is being worked on as soon as possible."
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 12620
Joined: 2010-05-22
A few years ago I did the lottery for the first time in probably 10 years.
1st number came up, I smiled.
2nd number came up, I laughed.
3rd number came up, I looked at it seriously thinking, nooo wayyyy.
I was right, thats all I got, damn.
It won a bit over £30, enough for the next 15 mostly wasted chances lol.
Although I think I'm slightly ahead overall, had plenty of 2 or 3 number wins, slightly luckier than average