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

Replace "target" with a checkpoint system #41

Open
smnhff opened this issue Feb 5, 2024 · 1 comment
Open

Replace "target" with a checkpoint system #41

smnhff opened this issue Feb 5, 2024 · 1 comment

Comments

@smnhff
Copy link

smnhff commented Feb 5, 2024

Currently, fuzzware supports the definition of a "target". A "target" is a point in the program that needs to be discovered once, and from then on, the fuzzing prefix to reach this point is prepended to all further fuzzing input in order to always pass that point in the program. This is very helpful to pass a boot process once and then continue fuzzing the actual application.

This approach hits its limits once this "target" is far enough into the program for the fuzzer to not reliably find that point in a given time. To improve upon this feature, fuzzware could implement a checkpoint system, that, in its simplest form, iteratively performs the "target" approach from above:
First, the analyst defines a list of targets. Fuzzware then performs the "target" step for each entry in the list, until the last entry is found. From there on, it performs its regular exploration.

@Scepticz
Copy link
Contributor

Scepticz commented Apr 3, 2024

Thank you for the pull request. As we discussed previously, I like the feature. Due to the number of changes I think we need some more testing. I am a bit strapped for time at the moment, so I would appreciate somebody help testing this.

Tobi

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

No branches or pull requests

2 participants