Closed Daft-Wullie closed 4 years ago
unsure if same as #78, reporting in case it's different.
For analysis, here is a package with:
attestation.ssz beacon.ssz output_beaconfuzz_debug.txt prysm_post.ssz
You can reproduce with:
../beaconfuzz_v2 debug beacon.ssz attestation.ssz attestation
FYI,
AttestationInvalid { index: 0, reason: BadCommitteeIndex }
Look similar than #78, let keep this one open as well for the moment.
Yup, confirmed this is a duplicate of #78
I've identified a fuzzer crash and am contributing to the security of Ethereum 2!
I've done and provided the following:
[FUZZ]
issue already refers to that crasherbeacon-fuzz
version or commit used.Info to Reproduce
Command run: e.g. `make fuzz_attestation-struct
Crasher file name: crash-e63668ea501e77231d973e7594bed483fbe5cbc5 crash-e63668ea501e77231d973e7594bed483fbe5cbc5.zip
beaconstate: adff0fb65525fcb1f08ecf09c1898dea.ssz
Client exercised: N/A
Fuzzing engine used (if applicable): libfuzzer
Crash output and stacktrace
re run crasher file with
ETH2FUZZ_BEACONSTATE=../eth2fuzz/workspace/corpora/beaconstate cargo +nightly fuzz run struct_attestation fuzz/artifacts/struct_attestation/crash-e63668ea501e77231d973e7594bed483fbe5cbc5
and got:Your Environment