byte-mutator
is a crate for defining a set of rules by which to mutate byte arrays. It's intented to be used as part
of a fuzzing workflow to configure how you want your input mutated. For example, you might want to do one pass where
you don't mess with the header of your message, and you only mutate the body -- or you could mutate them differently.
This example is configured to flip every bit in the bytes one at a time.
```rust let mut bytes = b"foo".tovec(); let mut mutator = ByteMutator::new().withstages(vec![Stage { count: 0, max: Some(24), mutations: vec![Mutation { range: None, mutation: MutationType::BitFlipper { width: 1 }, }], }]);
// Bytes in their original state assert_eq!(&bytes, b"foo");
// Perform a single mutation mutator.mutate(&mut bytes);
// We've flipped the first bit (little endian) // 0b1100110 -> 0b1100111, 103 -> 102, f -> g assert_eq!(&bytes, b"goo"); ```
This is an example of a mutator configured to flip bits forever. ```toml [[stages]] # Iteration count at which to start the loop (useful for starting over from a future state) count = 0
# A list of mutations to perform on this stage
[[stages.mutations]]
# Must be a variant of the MutatorTypes enum
mutation = {"BitFlipper" = {width = 1 }}
```
&mut [u8]
reference.Iterations
, just added a simple Option<usize>
for max
. Ryan Ragona – @ryanragona – https://github.com/ragona
Distributed under the MIT license. See LICENSE
for more information.
Always happy to see PRs or Issues.
To contribute:
1. Fork it (https://github.com/ragona/yourproject/byte-mutator)
2. Create your feature branch (git checkout -b feature/fooBar
)
3. Commit your changes (git commit -am 'Add some fooBar'
)
4. Push to the branch (git push origin feature/fooBar
)
5. Create a new Pull Requesti