Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address INTEL-SA-00219 #49

Open
RodelFMiguel opened this issue Nov 29, 2019 · 1 comment
Open

Address INTEL-SA-00219 #49

RodelFMiguel opened this issue Nov 29, 2019 · 1 comment

Comments

@RodelFMiguel
Copy link

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?

@tdelmas
Copy link

tdelmas commented Dec 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants