smite-ir: mutate byte params with repeated interesting bytes - #214
Open
erickcestari wants to merge 1 commit into
Open
smite-ir: mutate byte params with repeated interesting bytes#214erickcestari wants to merge 1 commit into
erickcestari wants to merge 1 commit into
Conversation
Collaborator
|
Ran into an issue with this change -- we can now actually create invalid private keys with repeated |
Byte parameter mutations could only fill with uniformly random bytes, which essentially never produces a field that is entirely 0x00 or 0xFF. Some targets only misbehave on such a field, e.g. CLN's funding_txid==0 assertion crash. Add repeated-fill mutations for both fixed and variable byte parameters, with the repeated byte biased toward INTERESTING_U8.
erickcestari
force-pushed
the
repeated-byte-mutation
branch
from
August 28, 2026 18:36
5c71a8d to
c0696be
Compare
Contributor
Author
True. I've fixed it by mutating and remediating the private key if it's invalid. It should keep the key in a range of |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Byte parameter mutations could only fill with uniformly random bytes, which essentially never produces a field that is entirely
0x00or0xFF. Some targets only misbehave on such a field, e.g. CLN'sfunding_txid==0assertion crash.Add repeated-fill mutations for both fixed and variable byte parameters, with the repeated byte biased toward
INTERESTING_U8.Closes #179