3 ms·
Is there any chance this could be exploitable from within a guest virtual machine, or does Intel's architecture only allow a hypervisor to communicate with the
by dhx 9y ago
Is there any chance this could be exploitable from within a guest virtual machine, or does Intel's architecture only allow a hypervisor to communicate with the firmware?
- jacquesm 9y agoIf it is remotely exploitable that means that if you're on the network you can do damage. So if that guest virtual machine has access to the same LAN or VLAN that your ME sits on then you might be in trouble. That's the whole problem here, this is an issue that allows a remote attack, not just a local one.
- pritambaral 9y agoEven so, it also allows a local attack. One that cannot be fixed without a firmware upgrade (now hope/pray/beg your OEM to release one). Yes, remote exploitability sucks hard, but that's not the "whole problem"; there's a bigger problem that just remote exploitability.
- tyingq 9y agoThey don't say how the local exploit works, other than mentioning that an unprivileged user can do it: "An unprivileged local attacker could provision manageability features gaining unprivileged network or local system privileges" I would go ahead and assume it's an issue on guest virtual machines. Maybe not, but since they don't explain the vector...