BIOSConnect code execution bugs impact millions of Dell devices :
https://www.zdnet.com/article/biosconne ... l-devices/
if we install DELL's recent bios/UEFI updates, how will this impact MX installs ?
- andrewjoseph
- Posts: 17
- Joined: Mon Jul 05, 2021 12:43 pm
Re: if we install DELL's recent bios/UEFI updates, how will this impact MX installs ?
AFAIK, this vulnerability is that BIOSConnect (an MS Windows application) trusts ANY wildcard certificate (not only dell's) from where to download BIOS updates.
So, ANYONE with a https wildcard certificate could download malicious "BIOS updates" on your computer.
But, BIOSConnect isn't for Linux.....
Anyway , AFAIK, it is a good practice to install BIOS and/or firmware updates.
BTW: See what kind of bad software is developed by BIOS manufacturers.
(Just imagine what would happen if apt-get trusted any certificate -- in the first place, such bad code would never see daylight in the opensource world)
So, ANYONE with a https wildcard certificate could download malicious "BIOS updates" on your computer.
But, BIOSConnect isn't for Linux.....
Anyway , AFAIK, it is a good practice to install BIOS and/or firmware updates.
BTW: See what kind of bad software is developed by BIOS manufacturers.
(Just imagine what would happen if apt-get trusted any certificate -- in the first place, such bad code would never see daylight in the opensource world)
Re: if we install DELL's recent bios/UEFI updates, how will this impact MX installs ?
Not always.andrewjoseph wrote: ↑Wed Jul 07, 2021 11:46 am
Anyway , AFAIK, it is a good practice to install BIOS and/or firmware updates.
Some BIOS 'updates' have introduced excessive CPU thermal throttling, others have locked out CPU undervolting.
Re: if we install DELL's recent bios/UEFI updates, how will this impact MX installs ?
Many BIOS and even Windows updates, at least for me, have the added "feature" of undoing any tweaks I've had to do in the BIOS to get the system to see and use the MX efi file. Purely a coincidence that that benefits Microsoft, right?