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

Status of attacks on chipyard-based boom #3

Open
austinharris opened this issue Dec 4, 2019 · 4 comments
Open

Status of attacks on chipyard-based boom #3

austinharris opened this issue Dec 4, 2019 · 4 comments

Comments

@austinharris
Copy link

austinharris commented Dec 4, 2019

I was able to successfully run the conditional branch mispredict and the indirect branch mispredict attacks with this chipyard version and the MediumBoomConfig:
ef404ef0ba6c471430120f13818cc5027225d877

However the return stack buffer attack did not recover the correct secret.

@jerryz123
Copy link
Contributor

The RAS in BOOM was disabled due to bugs.
We will push a version with a working RAS soon.

@abejgonzalez
Copy link
Collaborator

Thanks for re-testing it will all the changes that have happened to the core/SoC ecosystem recently!

@hz1490919302
Copy link

Thanks for re-testing it will all the changes that have happened to the core/SoC ecosystem recently!

Now RAS has been fixed in the latest boom, but I still can’t implement spectreRAS with the SmallConfigBoom and the chipyard. Can the current Boom protect against this spectre attack?

@jerryz123
Copy link
Contributor

The spectreRAS implementation in this repository is unfinished, as the README notes. Perhaps someone should finish this. It should be pretty straightforward to modify the x86 code example in the original Spectre Returns paper.

In general, BOOM does not have protection against RAS-based attacks.

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

4 participants