mirror of
https://github.com/The-Art-of-Hacking/h4cker
synced 2024-11-21 18:33:03 +00:00
Update README.md
This commit is contained in:
parent
6f96c8ec45
commit
b07836a135
1 changed files with 12 additions and 0 deletions
|
@ -24,3 +24,15 @@
|
||||||
- [DerbyCon 2016: Fuzzing basics...or how to break software](http://www.irongeek.com/i.php?page=videos/derbycon6/411-fuzzing-basicshow-to-break-software-grid-aka-scott-m)
|
- [DerbyCon 2016: Fuzzing basics...or how to break software](http://www.irongeek.com/i.php?page=videos/derbycon6/411-fuzzing-basicshow-to-break-software-grid-aka-scott-m)
|
||||||
- [TALOS Munity Fuzzer Tutorial](https://www.youtube.com/watch?v=FZyR6MgJCUs)
|
- [TALOS Munity Fuzzer Tutorial](https://www.youtube.com/watch?v=FZyR6MgJCUs)
|
||||||
- [A curated list of Fuzz-related topics](https://github.com/secfigo/Awesome-Fuzzing) maintained by [@secfigo](https://twitter.com/secfigo). Includes tools, books, free and paid courses, videos, and tutorials.
|
- [A curated list of Fuzz-related topics](https://github.com/secfigo/Awesome-Fuzzing) maintained by [@secfigo](https://twitter.com/secfigo). Includes tools, books, free and paid courses, videos, and tutorials.
|
||||||
|
|
||||||
|
## Types of Fuzzing Techniques
|
||||||
|
The following are the most common types of fuzzing categories:
|
||||||
|
|
||||||
|
### Mutation
|
||||||
|
Mutation-based fuzzers use samples of valid input that are mutated randomly to produce malformed input. A dumb mutation fuzzer can simply select a valid sample input and alter parts of it randomly. You can build in greater intelligence by allowing the fuzzer to do some level of parsing of the samples to ensure it only modifies specific parts or doesn’t break the overall structure of the input so it’s immediately rejected by the program. Some protocols or file formats will incorporate checksums that will fail if they’re modified arbitrarily. A mutation-based fuzzer should usually fix these checksums so the input’s accepted for processing or the only code tested is the checksum validation and nothing else.
|
||||||
|
|
||||||
|
### Generation
|
||||||
|
Generation-based fuzzers actually generate input from scratch rather than mutating existing input. They usually require some level of intelligence to construct input that makes at least some sense to the program, although generating completely random data would also technically be generation. Generation fuzzers often split a protocol or file format into chunks, which they can build up in a valid order, and randomly fuzz some of those chunks independently. This can create inputs that preserve their overall structure, but contain inconsistent data within it. The granularity of these chunks and the intelligence with which they’re constructed define the level of intelligence of the fuzzer. While mutation-based fuzzing can have a similar effect as generation fuzzing (as, over time, mutations will be randomly applied without completely breaking the input’s structure), generating inputs ensures this will be so. Generation fuzzing can also get deeper into a protocol more easily, as it can construct valid sequences of inputs applying fuzzing to specific parts of that communication. It also allows the fuzzer to act as a true client/server, generating correct, dynamic responses where these can’t be blindly replayed.
|
||||||
|
|
||||||
|
### Evolutionary
|
||||||
|
Evolutionary fuzzing’s an advanced technique, which we’ll briefly describe. It allows the fuzzer to use feedback from each test case to learn the format of the input over time.
|
||||||
|
|
Loading…
Reference in a new issue