vulnerabilities experimentation

We have three sources for vulnerabilities experimentation with SLUMPs:

- Memory disclosures from #7 (C code [here](https://github.com/KTH/slumps/tree/master/vulnerable_programs/report-web-assembly-memory-safety/c))
- Whitebox cryptographic programs mentioned in #27
- CVEs report for webassembly mentioned in #41
- TODO: Collect specific CVEs to test

**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)
- Try to execute in the browser
- Collect the profiler information from the DevTool
- Execute the same WASM code in SWAM and collect stack and memory traces

3 - Feed SLUMPs with the vulnerable program
4 - Collect variants
- For each variant: apply step 2

**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*
```
docker run -it --rm -v $(pwd)/out:/slumps/src/out jacarte/slumps:app https://raw.githubusercontent.com/KTH/slumps/master/benchmark_programs/rossetta/valid/no_input/Catalan_numbers.c Catalan_numbers.c
```