• Now's your chance win big! Join our community and get entered to win a RTX 2060 GPU, plus more! Join here.

    Meet Stan Dmitriev of SurrogateTV on the Pi Cast TODAY! The show is live August 11th at 2:30 pm ET (7:30 PM BST). Watch live right here!

    Professional PC modder Mike Petereyns joins Scharon on the Tom's Hardware Show live on Thursday, August 13th at 3:00 pm ET (8:00 PM BST). Click here!

Question Z170 Extreme4 – “This system is vulnerable” (CSME 11.8.50.3425)

Feb 8, 2020
6
0
10
0
With little chance of a Z170 Extreme4 BIOS update from ASRock, I’m just wondering if there is some other way to update the CSME firmware?

Currently running the latest 7.50 BIOS/CSME 11.8.50.3425 (2018/3/12) and an i7 6700k.
 
Feb 8, 2020
6
0
10
0
That’s my hope, but there seems little chance of an update with the age of the board and the last BIOS dating from 2018/3/12. I was just wondering if there was some other method of updating.

See here: https://www.intel.com/content/www/us/en/support/articles/000025619/software.html

To resolve, Asrock needs to provide an updated BIOS version or you need a different, more current, motherboard.

If you practice safe computing usage, you really don't have to worry too much about this.
 

COLGeek

Cybernaut
Moderator
That’s my hope, but there seems little chance of an update with the age of the board and the last BIOS dating from 2018/3/12. I was just wondering if there was some other method of updating.
You should never use a BIOS from any other source other than those provided by the manufacturer. Doing so is very risky. The likely outcome is a bricked motherboard.

On the Asrock site, there is a Beta version BIOS that is newer than the one you have. You could try using it (7.51). However, given the date and the provided notes, it is not a likely solution.

https://www.asrock.com/mb/Intel/Z170 Extreme4/#BIOS
 
Reactions: Alan Philp
Feb 8, 2020
6
0
10
0
It looks like the newer BETA was only for memory compatibility and predates any further Intel updates unfortunately.

I totally agree about not using a third party BIOS, but wondered if I missed a generic asrock wrapper that would keep secure boot and verification happy.

The latest updates further mitigate remote code execution and keeps the issue to local access. Looks like it cannot be 100% fixed though.
 

ASK THE COMMUNITY

TRENDING THREADS