Skip to content

A project to compare the performance of various fuzzers against 5 Node.js applications.

License

Notifications You must be signed in to change notification settings

uqcyber/NodeJSFuzzing

Repository files navigation

Copyright (c) 2020, 2021, Oracle and/or its affiliates.

Contributor: Trong Nhan Mai


NODE_JS_FUZZING

A small project to compare the performance of various of fuzzers against 5 Node.js applications. The list of applications involved in this project:

The list of fuzzers involved:

Presequisites

The docker images are built and tested with:

  • Docker version 18.09.1-ol, build b2a1f2a
  • docker-compose version 1.27.4, build 40524192

All the docker-compose.yml files are at version "2.0". For the docker-compose version support, please see here

Infrastructure

Infrastructure using Docker containers

The infrastructure to exercise 5 Node.js applications has three components:

  • Application Docker images
  • Fuzzer Docker images
  • Docker & docker-compose

With the help of docker-compose.yml, the infrastructure is started which allows fuzzer container to interact with our applications. The user can access those containers from the host machine.

Building and pushing docker images to Github registry

First create a personal token on github. Make sure that the token has enough privileges (i.e read,write:packages). Then run docker login.

$ docker login docker.pkg.github.com --username <your_username> -p <your_token>

Build your image and run docker tag (all names are lowercase)

$ docker build -t <image_name>:<tag> .

$ docker tag <image_name>:<tag> docker.pkg.github.com/<user_name>/<repo_name>/<image_name>:<tag>

Push the tagged docker image to repo

$ docker push docker.pkg.github.com/<user_name>/<repo_name>/<image_name>:<tag>

For more information, please see Github Docs.

Quick start

Docker-compose provides a quick and easy way to startup the applications.

  1. Head to the desired application's directory (for example: app_docker/nodegoat for NodeGoat).
  2. In the docker-compose.yml file, replace <name>:<tag> by the application's Docker image name. For example nodegoat:v1.
  3. Run: docker-compose up
  4. Docker-compose will handle the pulling and running those applications
  5. Then you can access the application via browser on localhost. (Please see README.md in app_docker for more information).

For apostrophe-boilerplate only: After the application has been started, we need to add an admin account. We do that by executing this command in the same directory with the docker-compose.yml file used:

$ docker-compose exec apostrophe node app apostrophe-users:add admin admin

The above command will add the user admin (first parameter) to the group admin (second parameter). After that you need to enter the password for this account (please use demo for admin to suit the auth script). Instructions taken from here.

Further instructions

  • Before using docker-compose.yml please provide it with the necesary image, or build your own following the instructions in app_docker.
  • All the applications are run with code coverage enabled by default. To disable code coverage, in the docker-compose.yml file, remove the --enable-coverage (and --babel for Juice-Shop) flag in the startup command.
  • The code coverage plugin uses a modified version of instanbul-middleware. The original repo is located here - license.
  • The instructions on how to work with fuzzers and get them to interact with our applications can be found in fuzzer_docker

Authentication

We also provide authenticating scripts for each applications. The output of these scripts will be a set of tokens that can be used in the scanning process of fuzzers. Please refer to README for how to use the scripts.

About

A project to compare the performance of various fuzzers against 5 Node.js applications.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •