ZcashFoundation ZEBRA
ZEBRA: Consensus divergence via P2SH sigop undercount in pure-Rust disabled-opcode parser
ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, Zebra can accept a block that zcashd rejects because the P2SH signature-operation counter undercounts redeem scripts containing a disabled opcode followed by signature opcodes. In zebra-script/src/lib.rs, p2sh_input_sigop_count used the pure-Rust script::Code::sig_op_count path, whose try_fold parser stops at disabled opcodes such as OP_CODESEPARATOR and returns only the partial count accumulated before the error. The zcashd reference implementation continues static signature-operation counting through disabled opcodes, so an attacker can broadcast P2SH spends that Zebra counts below MAX_BLOCK_SIGOPS while zcashd counts above the 20,000-operation limit. If a Zebra miner includes those transactions, Zebra validators accept the block while zcashd validators reject it, creating a consensus chain split that affects network integrity and availability without requiring the attacker to produce a block. This issue is fixed in version 4.5.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 4.5.0
Fixed in 4.5.0
Mitigation
Upgrade zebra to 4.5.0 or later.
References
- Vendor advisory github.com/ZcashFoundation/zebra/security/advi…
- Patch github.com/ZcashFoundation/zebra/commit/1440b4…
- Release notes github.com/ZcashFoundation/zebra/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.