Better workflow
This commit is contained in:
47
README.md
47
README.md
@@ -26,25 +26,36 @@
|
|||||||
Bolt is in alpha phase of development which means it's full of bugs. Any production use of this tool discouraged.
|
Bolt is in alpha phase of development which means it's full of bugs. Any production use of this tool discouraged.
|
||||||
Pull requests and issues are welcome. I also suggest you to put this repo on watch if you are interested in it.
|
Pull requests and issues are welcome. I also suggest you to put this repo on watch if you are interested in it.
|
||||||
|
|
||||||
### Current Features
|
### Workflow
|
||||||
- Crawling
|
|
||||||
- Complete HTTP Support
|
|
||||||
- Checks
|
|
||||||
- Entropy
|
|
||||||
- Replay attack
|
|
||||||
- Absence of CSRF protection when requested from a mobile
|
|
||||||
- Removing CSRF token parameter from request
|
|
||||||
- Removing CSRF token from parameter
|
|
||||||
- Requesting resources with a fake token
|
|
||||||
- Potenial race condition
|
|
||||||
|
|
||||||
### Features to be added
|
#### Crawling
|
||||||
- Support CSRF tokens in cookies
|
Bolt crawls the target website to the specified depth and stores all the HTML forms found in a database for further processing.
|
||||||
- Referrer and Origin based checks
|
|
||||||
- Checks
|
#### Evaluating
|
||||||
- True entropy of tokens
|
In this phase, these three things are checked:
|
||||||
- Checking if server checks the token to a specific length
|
- Forms without CSRF protection
|
||||||
and more...
|
- Weak tokens
|
||||||
|
- Comparison of token with various hashes
|
||||||
|
|
||||||
|
##### Comparing
|
||||||
|
This phase focuses on detection on replay attack scenarios and hence checks if a token has been issued more than one time.
|
||||||
|
It also calculates the average [levenshtein distance](https://en.wikipedia.org/wiki/Levenshtein_distance) between all the tokens to see if they are similar.
|
||||||
|
|
||||||
|
##### Observing
|
||||||
|
In this phase, 100 simultaneous requests are made to a single webpage to see if same tokens are generated for the requests.
|
||||||
|
|
||||||
|
##### Testing
|
||||||
|
This phase is dedicated to active testing of the CSRF protection mechanism.
|
||||||
|
It performs the followings checks
|
||||||
|
- Mobile CSRF protection test
|
||||||
|
- Request without CSRF token parameter
|
||||||
|
- Request without CSRF token parameter value
|
||||||
|
- Request with a self generated token
|
||||||
|
|
||||||
|
##### Analysing
|
||||||
|
Various statistical checks are performed in this phase to see if the token is really random.
|
||||||
|
Following tests are performed during this phase
|
||||||
|
- Monobit test
|
||||||
|
|
||||||
### Usage
|
### Usage
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user