CVE-2023-24932
- Thread starter Mervyn Haynes
- Start date
- Watchers 4
-
Be sure to checkout “Tips & Tricks” Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!
/Steve. -
BootAble – FreeDOS boot testing freeware
To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.
GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.
The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.
You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.
(You may permanently close this reminder with the 'X' in the upper right.)
I have a distinct memory of him talking about something related, but I don't think he has discussed this specific vulnerability, at least I find no evidence of that specific CVE. I know he has mentioned other secure boot issues, and UEFI driver compromises in the last couple of years.
I haven't talked about that one, Mervyn. I don't have any strong reasoning for not having mentioned it, though I don't recall exactly when I saw it and what other news it may have been competing with. And also, it may have been my own bias, since I've never really bought into the whole secure boot concept. It has always felt like Microsoft spending a huge amount of effort on something that's not really a large problem (compared to so many of their other problems that are) and that it cannot really be fixed -- as we continually see bypasses and ways around it and mistake being made there. It's certainly not "one and done."
Perhaps you could share all your concerns about secure boot in an episode when there is a quiet news week? I am sure listeners would be interested. I don't think Microsoft is going to resolve it until the first half of this year. As I understand it, the "workaround" they have at the moment, is to add a registry key manually. This will make all backups unusable, and any recovery boot media you have also unusable. Even a reformat & reinstall the OS will not work after this "fix"! (KB5025885)
Last edited:
