You can now run software like EFIgy or my EFIver.py to see if you are using the latest EFI update from Apple, but that doesn’t necessarily mean that you are using the latest and greatest from Intel. Not for the following models:
File : IM144_0183_B00.scap (iMac14,4) ME version: 18.104.22.1686 Latest : No File : IM151_0211_B00.scap (iMac15,1) ME version: 22.214.171.1242 Latest : No File : IM162_0212_B00.fd (iMac16,2) ME version: 126.96.36.1990 Latest : No File : IM171_0110_B00.fd (iMac17,1) ME version: 188.8.131.520 Latest : No File : IM181_0151_B00.fd (iMac18,1) ME version: 184.108.40.2069 Latest : No File : IM183_0151_B00.fd (iMac18,x) ME version: 220.127.116.119 Latest : No File : MBP114_0177_B00.fd (MacBookPro11,4) ME version: 18.104.22.1685 Latest : No File : MP61_0120_B00.scap (MacPro6,1) ME version: 22.214.171.1241 Latest : No
This shows us a limitation of EFIgy and my very own EFIver.py script. One that I would like to address soon. Speaking of which, the latest beta (v3.2) now also runs with Python3 – required for Windows and Linux – but you’ll need PyObjc.
And while I don’t really know if this opens un-patched attack vectors, or if this is Apple’s fault (but Intel?) but I like to keep my Mac safe. As much as I can, and then something like this isn’t really helping me.
Thanks to Plato Mavropoulos for his ME Analyzer!