← All insights
RELEASEZcash Foundation

Zebra 6.3.0: sync and peer security fixes

A recommended security release that resolves four security advisories on block sync and peer scoring. It also adds the getdeprecationinfo RPC and new default DNS seeders.

The Zcash Foundation released Zebra 6.3.0 as a recommended security release. It resolves four security advisories found in block sync and peer scoring and strengthens enforcement of inbound bans. These include peer-induced delays in tip discovery, sync stalls near the tip, and loopholes that let malicious peers get honest peers banned or evade bans. All operators were advised to upgrade.

The four advisories are as follows. GHSA-g95h-hw6g-pvgv (high) is a problem where a forged block body that changes only the coinbase scriptSig can delay tip discovery. GHSA-qhr3-cvch-5fh2 (medium) is a problem where scoring far-ahead blocks amplifies bans of honest peers, and GHSA-8hh2-hrf2-cqf4 (medium) is a problem where peers that gossiped invalid blocks were not scored. GHSA-h8m8-844p-v3m9 (medium) is a problem where sync stalls on a single-hash response.

There are further security improvements. Inbound connections arriving from IPv4-mapped IPv6 addresses are now normalized to standard IPv4 addresses, fixing a problem where bans did not apply and the connection was counted twice against the per-IP limit. Banning a peer removes every entry for that IP from the address book, and banned IPs are not chosen as reconnection candidates. GHSA-2p4c-3q4q-p463 (high), already fixed in 6.2.1, is now disclosed: a problem where NU6.3 (Ironwood) V6 transactions could stall block verification with invalid proofs that are expensive to verify.

New features include the getdeprecationinfo RPC, which reports the end-of-support height and estimated time, the default DNS seeders seeder.zec.rocks and seeder.testnet.zec.rocks, and Prometheus metrics broken down by network, direction and address family. getblocksubsidy still returns funding-stream metadata after NU6.1, and blocks whose total chain value pool exceeds MAX_MONEY are rejected.

Users of the zebra-consensus crate should know that the transaction verifier was split into separate ones for blocks and the mempool and changed to the transaction::MempoolRequest and MempoolResponse types. There is no behavioral difference for operators, but library users must update their code. The release is available from GitHub, crates.io and Docker Hub.

This summary is based on the original; check the original for exact details.