Impact
SkipBlockProof::verify computes its quorum check using BitSet.len(), then iterates BitSet indices and casts each usize index to u16 (slot as u16) for slot lookup. If an attacker can get a SkipBlockProof verified where MultiSignature.signers contains out-of-range indices spaced by 65536, these indices inflate len() but collide onto the same in-range u16 slot during aggregation.
This makes it possible for a malicious validator with far fewer than 2f+1 real signer slots to pass skip block proof verification by multiplying a single BLS signature by the same factor.
Patches
The patch for this vulnerability is formally released as part of v1.3.0.
Workarounds
No known workarounds.
References
See PR.
Impact
SkipBlockProof::verifycomputes its quorum check usingBitSet.len(), then iteratesBitSetindices and casts eachusizeindex tou16(slot as u16) for slot lookup. If an attacker can get aSkipBlockProofverified whereMultiSignature.signerscontains out-of-range indices spaced by 65536, these indices inflatelen()but collide onto the same in-rangeu16slot during aggregation.This makes it possible for a malicious validator with far fewer than
2f+1real signer slots to pass skip block proof verification by multiplying a single BLS signature by the same factor.Patches
The patch for this vulnerability is formally released as part of v1.3.0.
Workarounds
No known workarounds.
References
See PR.