effected
Comment on New UEFI vulnerabilities send firmware devs industry wide scrambling
SnotFlickerman@lemmy.blahaj.zone 9 months agoThe nine vulnerabilities that comprise PixieFail reside in TianoCore EDK II, an open source implementation of the UEFI specification. The implementation is incorporated into offerings from Arm Ltd., Insyde, AMI, Phoenix Technologies, and Microsoft. The flaws reside in functions related to IPv6, the successor to the IPv4 Internet Protocol network address system. They can be exploited in what’s known as the PXE, or Preboot Execution Environment, when it’s configured to use IPv6.
Not all hardware manufacturers are effected and it’s based on a specific open source implementation of UEFI.
corsicanguppy@lemmy.ca 9 months ago
xan1242@lemmy.ml 9 months ago
Aren’t AMI, Insyde and Phoenix providers for 98% of PC (be it board or OEM) vendors though?
And AFAIR, TianoCore is basically used everywhere by everyone as a base except maybe Apple.
SnotFlickerman@lemmy.blahaj.zone 9 months ago
You may be right, I didn’t think those three were that much of the market, but maybe I’m wrong.
I thought Tiano was a reference UEFI developed by Intel?
EDK and EDK II are open source projects that spun off of that reference developed by Intel.
I suppose the main thing I was trying to get across is that OP seemed to be blaming motherboard manufacturers for bad code… but this is the base open source code that is causing the issues, prior to implementation by motherboard manufacturers.
xan1242@lemmy.ml 9 months ago
I am pretty sure TianoCore is also used by AMD systems as a reference as well.
Here’s a similar situation that happened in 2019 at Lenovo’s site
support.lenovo.com/cl/es/solutions/LEN-22660
AMD systems are listed as well.
As for most board vendors nowadays, I think they barely do anything with the code itself and just create the setup utility and boot logos. It is highly likely that they’re affected too.