-
Notifications
You must be signed in to change notification settings - Fork 11
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
vulnerabilities experimentation #42
Comments
It can take a while, taking into account that the souper exploration can be expensive. However, the timeout in this case (second line in your screenshot) is for half hour. In the experiments that we ran the time for an answer was 2863.46 seconds. |
@Jacarte I am able to get into the interactive mode using this command(docker run -it --rm -v root@5831e19c674c:/slumps/src# python3 slumps.py interger_overflow.c |
Change the python interpreter to python3.7 instead of python3, |
Should be something like this
You are missing the second part for the vulnerabilities volume, therefore, the files are not in the slumps root. |
Sorry my mistake, you are overriding the src folder thats why you are not seeing the scripts slumps.py. Change the second volume to |
I see...try to remove the |
Changing the entrypoint for the container bypasses the initialization of redis-server service. To launch it again, run |
We have three sources for vulnerabilities experimentation with SLUMPs:
Experiment steps:
1 - Port the vulnerable code to WebAssembly using SLUMPs and collecting the original program without optimizations
2 - See if the problem persists in the V8 context (already tested in #7 with emcc)
3 - Feed SLUMPs with the vulnerable program
4 - Collect variants
Notes
In the case of the CVEs, we also need to test if the CVEs related to Binaryen persist after the SLUMPs phase
Use the dockerized SLUMPs app
For example
The text was updated successfully, but these errors were encountered: