Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactored mutation functions to offer a generic toolkit for mutating data #37

Open
wants to merge 6 commits into
base: dev
Choose a base branch
from

Conversation

f0rki
Copy link

@f0rki f0rki commented Jan 11, 2024

useful when writing custom input formats/mutators.

  • added a TextInput type that does some mutations specific to.. well text input.
  • added a havoc module with several mutation functions usable by custom mutators, if you "just want to mutate a bunch of bytes".

@f0rki f0rki marked this pull request as ready for review January 23, 2024 16:12
… data.

* Added a `TextInput` type that implements mutators useful only for text-based inputs.
* Added several havoc mutation helper functions usable by custom mutators.
* Added helper functions to mutate arrays/vec of numbers.
* Generalized a couple of helper functions to be generic over all copy types, etc.
…ata.

Fixed some issues with the text-based mutator code along the way.

* The new example has two artificial vulnerabilities that can be triggered
  using the right arguments to a JS function.
* Added some tweaks to the text-based mutations.
* In order to avoid breakpoints on longjump and similar functions, we
  need to properly detach gdb. This requires a pattern of
  ```
    __asm("int3");
    sleep(1);
    __asm("vmcall");
  ```
  and also the `SNAPSHOT_GDB_MODE="detach"` definition. To allow
  gdbsnapshot.py to do its thing, but then also to detach gdb before the
  snapshot is triggered.
Michael Rodler and others added 4 commits April 10, 2024 13:11
…n that can e.g., splice multiple lines of text from another corpus entry
…d more interesting values.

* Previously those arrays contains `0, 1, 2, 3, 4` repeatedly, because
  they include `u8::MIN` and `u16::MIN`, which both is just `0`.
* Now they also include the `::MAX` values for the signed integer types,
  which together with the unsigned `::MAX` covers the whole range
  of signed types too.
…tion.

+ some fixes and a `MockRng` type useful for tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant