There is a security advisory that suggests that structures be aligned so that data inside the enclave memory should avoid putting sensitive data in DWORD0 and DWORD1 of the cache line.
"Organize the code/data within enclave memory to avoid putting sensitive materials in DWORD0 and DWORD1 of cache line. The effectiveness of this mitigation is dependent on the ability for the software to avoid the affected memory region. To assist the enclave application providers to modify their code, Intel is releasing SGX SDK update (Windows version 2.5.101.3, Linux version 2.7.101.3) with new memory allocation APIs to avoid the affected memory region. More details about the APIs can be found here."
Is there a plan to mitigate this vulnerability in SGXSSL?
There is a security advisory that suggests that structures be aligned so that data inside the enclave memory should avoid putting sensitive data in DWORD0 and DWORD1 of the cache line.
"Organize the code/data within enclave memory to avoid putting sensitive materials in DWORD0 and DWORD1 of cache line. The effectiveness of this mitigation is dependent on the ability for the software to avoid the affected memory region. To assist the enclave application providers to modify their code, Intel is releasing SGX SDK update (Windows version 2.5.101.3, Linux version 2.7.101.3) with new memory allocation APIs to avoid the affected memory region. More details about the APIs can be found here."
Is there a plan to mitigate this vulnerability in SGXSSL?