Intel in Denial of the Latest SGX Secure Enclave Vulnerability

in STEMGeeks2 years ago

Another vulnerability and exploit named VoltPillager has been published for Intel Corporation's SGX security technology. The attack itself is simply a hardware version of a previously discovered PlunderVolt software vulnerability where voltage to the chip was manipulated to undermine SGX enclave protections. PlunderVolt was able to recover secret information like encryption keys from Intel’s hardened security SGX vault, but a patch has been released to close the risks. However, VoltPillager bypasses that patch by directly manipulating voltage on the hardware itself.

The hardware to accomplish this feat is very inexpensive, coming in at around $36. It does however require physical access to the motherboard to install the hardware hacking device.

This is where the most disturbing aspect of this narrative emerges: pure denial by Intel. Intel has apparently stated to news outlets and the vulnerability researchers that they don’t consider this a vulnerability because, according to Intel, they aren’t responsible for whatever happens if someone opens the case of a PC or server. Therefore, it appears they have no intentions of fixing something they choose to not classify as a vulnerability.

How convenient! Avoid dealing with the problem by saying it isn't a problem.

Once again it appears that Intel’s legal and marketing teams are in control of security policy. This is a classic denial of responsibility.

The simple fact is that SGX has one purpose: to be a secure vault embedded in Intel’s chips. That vault has been cracked. It does not matter how, it is Intel’s responsibility.

Dodging accountability speaks volumes to how any organization views, invests, and handles product security.

Step up. If your super-secret SGX vault is being cracked, then it does not matter how. Own it and figure out mitigations.

As a shareholder and cybersecurity expert, I am gravely disappointed!

This is security, not a marketing spin-control exercise or avoid-the-liability legal game. It is time to replace the leadership that is allowing lawyers and marketeers to define your product security policy. You are losing valuable trust with your customers and undermining the confidence in digital technology adoption.

Posted with STEMGeeks


So, with the same logic, software developers shouldn't recognize vulnerabilities when their code is decompiled. Bah!!