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

Need to restrict SBIs the enclave can use #25

Open
dayeol opened this issue Mar 11, 2019 · 1 comment
Open

Need to restrict SBIs the enclave can use #25

dayeol opened this issue Mar 11, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@dayeol
Copy link
Contributor

dayeol commented Mar 11, 2019

Now SM is embedded into the bbl, which basically provides a lot of SBI that can enable DoS against the OS as well as some potential attacks.
For example, the enclave can shut down the entire machine using an SBI, and also request IPIs (e.g., TLB flush).
Once we make the SM keep track of the CPU states, we should be able to put some gaskets in those interfaces that prevents enclave from doing these.

@dkohlbre
Copy link
Collaborator

This should, imo, be part of our rework of enclave lifecycles into explicit fsms.
We can define the valid hart transitions along with the valid enclave state transitions and check it all at once on the SBI call.

@dkohlbre dkohlbre added the enhancement New feature or request label Mar 11, 2019
@dayeol dayeol added this to To do in Release (0.5) Sep 25, 2019
@dayeol dayeol assigned dayeol and ghost and unassigned dayeol Sep 25, 2019
@dayeol dayeol moved this from To do to In progress in Release (0.5) Dec 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Release (0.5)
  
In progress
Development

No branches or pull requests

2 participants