Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[Fuzzing] Crash on nfuzz_attestation #659
I think I've narrowed it down:
Because a larger index is allowed through,
@djrtwo I'm not certain re concensus tests, as this is effectively a "crash" of nim-beacon-chain, when it should return false (allowing nimbus to continue running).
In pyspec, this would be triggering an AssertionError anyway. If the above understanding of the bug is correct, an equivalent bug in the pyspec would be for
If the tests are only checking whether an assert is triggered, they would not be able to differentiate between these.
Can someone confirm whether my understanding is correct?
Interesting, I see.
That said, this codepath is clearly not triggered in Nimbus during the consensus tests. It seems likely that we can and should craft a consensus test that would trigger this code path.
I'll monitor this thread and make a call when y'all post a fix