Windows 10: Flaws found in Intel Management Engine (ME), TXE and SPS

Hi,

MEUpatetool.exe is for flashing MEI chipset, the PEUpdater.exe is ASUS tool for scheduled checking for updates on their servers, it runs in the background as a service.

Cheers, *Wink

 

Open 7Zip, work your way to the download, right click, select CRC, and then select SHA-256, it will create the MD5 and then compare it to the one on the site.

 

So which do I install first? I only want to apply the fix to patch up the security issue.

 

So what exactly am I pointing 7zip too here? This is the Fix/Patch that ASUS provide. This is why I'm confused with it all. It's not just a single file to install.

 

Do not open the downloaded zip file, you want the SHA 256 number for the complete folder.
Also if you have installed(not the portable version the .exe version) 7Zip 64bit .exe version, it is also integrated in the Windows shell, and is included in the right click menu too:

 

Thanks Cliff for your help and taking the time and trouble to post screenshots for me. I've got my ME Driver sorted out now as suggested by ASUS. All I have left to do now is hope someone can advise regarding the two .exe files in the ME security fix/patch from ASUS.

Will the main MEUpdate Tool.exe take care of everything else in the zip folder (including the PEUpdater), or do I have to run the PEUpdater.exe separately? I guess what I'm saying is, have ASUS bundled in two separate things for me to do here or is it just the MEUpdater Tool itself?

 

Gigabyte seems clueless on this and don't know when a new BIOS will be released for my board.

 

Same with Asus, seems clueless when I emailed them on this issue, so far just replied keep checking your Driver & Tools section for your model or Asus news section for further updates.

", we have taken your information and it has document for review to provide a solution once available. Note that once an update is available regarding a possible options for the issue reported, we will update you and all our valued customers at that point. Please feel free to check here for any update on this or anything else at anytime: ASUS Global"

Guess all I can do now is continue to wait

 

Hi,

The drivers show a differnt version number then the MEI software. That's normal for that version and the latest one as well.
Which is 10.7.0.1054, drivers are still 1045.

Cheers, *Wink

 

ASUS is definitely not clueless. They have issued an ME Update Tool for some of their affected motherboards. This is the entry for the Prime Z270-A (posted 11-22):

 

Hmmm no tool on my system download page yet, System is G11CD , unknown motherboard inside, as can't find any info on that aspect

 

I'm not sure you read my post completely. Anyway...

Gigabyte confirmed my suspicion that line #2 of the F7 BIOS in the USA was added later as shown by two different locations...

Gigabyte USA....




Gigabyte Global....




In fact they initially denied my claim that line 2 was there until I pointed them to the USA site. With that they say they'll have to contact Gigabyte headquarters to sort the issue. Bottom line is the F7 BIOS is NOT a fix for the IME flaw. And that both BIOS's are the same July BIOS addressing the HT flaw only. Those needing a BIOS update for the Z270 boards addressing the IME flaw will have to wait till then.

 

Before *Sad






After *Party

 

it's usually silk screened on the MB PCB ...... try opening the case and look...

or enter the Bios and see what the ME Version is....as far as I know if it is less than 11.0 like my Asus X99A-II (9.1.37) it is not vulnerable , only machines with an ME Firmware above 11 are effected.

 

The easy way is open Device Manager