Automatic exploit generation for Node.js applications. See examples
git clone https://github.com/formalsec/explode-js.git
cd explode-js
opam install . --deps-only
dune build
dune runtest
explode-js on your path by running:dune install
For benchmarking and evaluation see bench
In this project I adopted some practices that made some parts of the code more readable to me. So please use them:
For file paths: <something>_file, e.g., input_file,
scheme_file, original_file.
For dir paths: <something>_dir, e.g., nas_dir or workspace_dir.
For paths which may represent a dir or a file: <something>_path, e.g., input_path, output_path.
For the data of a file: <something>_data, e.g., module_data.