test: Fuzz execution of a single instruction with afl-fuzz #37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joonazan
force-pushed
the
symbolic-execution
branch
from
172cc0f to
5ce1dde
Compare
montekki
reviewed
May 27, 2024
montekki
reviewed
May 27, 2024
joonazan
force-pushed
the
symbolic-execution
branch
from
1e53af6 to
db8e97a
Compare
montekki
approved these changes
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces stack, program and heap with mocks that just contain one value and crash if multiple addresses are accessed. Fuzzes the execution of a single instruction.
The default settings of libFuzzer don't work for me and it doesn't tell what is going wrong, so I wrote this for afl-fuzz instead.
Afl explores lots of instructions in a matter of seconds, though the crashes it finds are not real ones yet because the test is still missing a state validity check.
The validity check should check that fat pointers are well-formed etc. The test should not be run if the initial state is invalid. The test should panic if the state is no longer valid after running an instruction.