Intel Management Engine vulnerability SA-00086 |
Post Reply | Page <1 5678> |
Author | ||
Kathrys
Newbie Joined: 23 Nov 2017 Status: Offline Points: 1 |
Post Options
Thanks(0)
|
|
Most motherboard manufacturers have already issued an update about incoming BIOS and software updates and we get silence?
I guess my next MB won't be an Asrock. |
||
soulstealer
Newbie Joined: 30 Sep 2016 Location: Hon Status: Offline Points: 76 |
Post Options
Thanks(0)
|
|
daddyo
Newbie Joined: 30 Oct 2017 Status: Offline Points: 54 |
Post Options
Thanks(0)
|
|
It was surprising to see how patronizing a moderator was regarding this issue. For those who have NOT read Intel's statement yet, they clearly have placed the initiative to resolve this serious security hole on the OEM providers, which Asrock would be in the case of motherboards.
Considering that any consumer Intel CPU made since fall of 2015 is affected, you can expect there will be attempts to make use of this vulnerability wherever it is unpatched. I await Asrock's official response. -- Edit-- I did notice on their website that ME engine and CPU microcode updates have been released on some server motherboards, and 300 series chipset based motherboards... I hope more will come! I just bought my z270 extreme4 a month ago. I would expect them to issue updates for 200 and 100 series motherboards as well.
Edited by daddyo - 23 Nov 2017 at 2:29am |
||
Arukado_
Newbie Joined: 22 Nov 2017 Status: Offline Points: 12 |
Post Options
Thanks(0)
|
|
Some hint in there. Did you run it with admin priviliges? |
||
japau
Newbie Joined: 06 Nov 2017 Location: FIN Status: Offline Points: 6 |
Post Options
Thanks(0)
|
|
Hi JZ,
Downloaded the file and followed the installation (windows64) like in youtube but it doesnt want to install on Z370 Taichi with BIOS 1.20 Error log as follows, Error 8193: Fail to load MEI device driver (PCI access for Windows) Above error is often caused by one of below reasons: Administrator privilege needed for running the tool ME is in an error state causing MEI driver fail MEI driver is not installed |
||
soulstealer
Newbie Joined: 30 Sep 2016 Location: Hon Status: Offline Points: 76 |
Post Options
Thanks(0)
|
|
yeah, thank you. i agree with you, this issue is not be taken lightly. i would argue that actually this is a production flaw in terms of warranty.
Edited by soulstealer - 23 Nov 2017 at 1:54am |
||
Arukado_
Newbie Joined: 22 Nov 2017 Status: Offline Points: 12 |
Post Options
Thanks(0)
|
|
Thanks JZ but I'll stick to that same statment as soulstealer made on original topic:
FWUpdLcl64 file is of course Intels flasher but nobody knows what is inside bin file. As far as we know this file can by legit or it can be another type od vulnerability just pretending to be the pacht. So if it's works Asrock should post it on their website. Edited by Arukado_ - 23 Nov 2017 at 1:30am |
||
J Z
Groupie Joined: 09 Sep 2016 Location: Germany Status: Offline Points: 976 |
Post Options
Thanks(0)
|
|
Kind Regards,
JZ https://shop.JZelectronic.de - Der Shop mit ausgesuchter ASRock Profi Hardware https://www.facebook.com/asrock.de |
||
Arukado_
Newbie Joined: 22 Nov 2017 Status: Offline Points: 12 |
Post Options
Thanks(0)
|
|
Have you read anything on Intel's website about this vulnerability? I don't think so Intel is aware of this vulnerability and the solution is to upgrade ME to newer version which can be done by BIOS upgrade i think. Dell and Lenovo already made a statement about this and working on new BIOS / firmware updates.
There's no problem with Intel's processor it's a problem with Intel's chipset and moreover firmware update should be deployed by system manufacturers as Intel said. So instead of being smart-ass and telling me to post something on Intel forum maybe next time read the whole post and then research topic a little more cos as I wrote in my first post Intel already told us to go to ours system manufacturers and Dell and Lenovo respond quickly. Furthermore why "we" and by "we" I ment users have to deal with this kind of attitude from manufacturers? I should not care which problem is this Intel's or Asrock's! This two company should talk with each other and give theirs customers working solution. More topics about this vulnerability occured on internet: https://rog.asus.com/forum/showthread.php%3F97618-When-will-we-see-firmware-updates-for-INTEL-SA-00086-for-X299 http://www.ocdrift.com/gigabyte-implements-safety-measures-against-intel-me-and-txe-security-vulnerabilities/ |
||
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
|
Why are you asking a mother board manufacture about a problem with a product they do not manufacture or sell? Why is a mother board manufacture responsible for any potential or existing flaw in a product they have not designed, manufactured, or marketed? Any fix for this situation can only come from Intel. A mother board manufacture cannot and should not speak for Intel about this situation. Intel is the best and only true source for any information about this situation. Have you posted a question in Intel's processor forum about this? |
||
Post Reply | Page <1 5678> |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |