Bishop is a vulnerability scanner that searches websites in the background while you browse, looking for exposed version control systems, misconfigured administrative tools, and more.

It works by searching for files with a given path on the current URL path and all parent paths, applying given regex to the results to check for proof positive of a vulnerable location. If the path returns 200 and matches the regex, it's flagged as vulnerable and alerts you. All rules are run on all directories in a set of time-staggered background XHR requests, so network throughput remains high at all times.

Bishop comes with a set of rules that hunt for the lowest hanging fruit, but the rule system is entirely extensible - rules are regular expressions that are run on specified directories, so if you can turn it into a regex, Bishop will look for it. Try loading Bishop with the demo ruleset and see how it works. The risk classification allows you to set different tiers of vulnerability so applications can be tested to stricter or looser security guidelines.

Bishop is intended SOLELY for legal use on web servers that you control or are permitted to scan, and the developers are not responsible for how you choose to use this software. Be safe and legal with this tool.

Bishop is MIT licensed and open source; contribute at https://github.com/jkingsman/bishop.

After either installation method, you'll need to setup your inclusion whitelist (see the introduction on first run for more info).

Download from the Chrome Web Store.

You'll need node and npm set up on your system (which is beyond the scope of this README), and gulp installed (npm install -g gulp if you don't already have it).

1. Clone this repo:

git clone [email protected]:jkingsman/bishop.git

2. Move into it:

cd bishop

2. Install the gulp dependencies:

npm install

3. Make sure the build directory is empty:

gulp empty

4. Build it, using any of the following commands:

If you have a general rule that you think others could find helpful, feel free to PR it. The fields are pretty self explanatory and match the GUI rule addition interface. The uid field can be left as is; it's just adding the unique ID for the rule. Risk is intended to describe the relative risk that such a vulnerability would indicate, allowing you to include stricter or looser security requirements for different applications.

• Bishop is built on sending background XHR requests, many of which will result in 404's. These will show up in your console log, so be aware of that when browsing. If you feel comfortable ignoring 404's, you can check the "Hide network messages" box at the top of the console window.

• The import formats are as follows:

  • rules

    • [{"description":"a few words descripting it","enabled":true,"name":"The Rule Name","risk":"low","searchString":"the regex to execut","uid":"random hex ID","url":"what URL addition (if any) to run the regex on"}, {...}]

  • sites

    • [{"rule":"matched rule name","uid":"random hex uid","url":matched URL"}, {...}]

MIT.