Skip to content
Crypto.world

The Ledger

Zebra 7.1.0 fixes ten Zcash node security advisories

Zcash Foundation says Zebra 7.1.0 addresses ten security advisories, including issues that could stall synchronization or exhaust node memory. The release adds diagnostic metrics and peer recovery, and upgrades from version 7.0.0 do not require a resync.

Zebra 7.1.0 fixes ten Zcash node security advisories

Ten advisories addressed

Zebra 7.1.0 closes ten Zcash node security advisories, including flaws that could interrupt synchronization or exhaust memory, according to a Zcash Foundation post published November 16. The release also adds sync and memory diagnostics, automatic peer recovery and clearer errors.

The Foundation says most of the advisories involved ways a network peer could stop a Zebra node catching up with the chain or cause it to run out of memory. Some issues affected only initial sync, while others could affect nodes already synchronized; the post says every node should upgrade.

Sync and memory risks

A peer could send forged blocks as initial sync moved from checkpoints to full validation, halting the process, the Foundation says. The update rejects those blocks and bans the peer. Two related flaws involved blocks with rewritten heights: Zebra now checks that block contents match the header, bans the peer and requests the block from another source.

Another advisory concerned transparent address-balance requests through the getaddressbalance RPC or lightwalletd. The Foundation says each request copied all recent blocks, so many simultaneous requests could exhaust memory; the updated requests read only the needed data. Requests for getaddressutxos and getaddresstxids also no longer copy every recent UTXO and transaction for the requested addresses.

A peer could also repeatedly restart block-download rounds by including already-known blocks in its reply. Zebra now skips those blocks and continues with the rest, according to the post. Queues holding blocks for checkpoint verification or awaiting parent blocks also had no memory limit; they now have limits, and sync requests a needed block again if it was dropped.

In another case, a peer sending a forged copy of a block first could cause the honest peer that supplied the real block to be banned without being penalized itself. The fix assigns responsibility to the peer that sent each block. The Foundation also says the mempool now checks the standard limit of 4,000 signature operations before verifying signatures on nonstandard transactions; block validation is unchanged.

For rejected transactions, the previous order of checks could leave proof-verification work running even after the mempool rejected a transaction. The update runs cheaper checks first, according to the release post.

Diagnostics and upgrade details

Other changes limit how much a peer can fill a node’s download queue, prevent an invalid block from cancelling unrelated downloads and time out stalled verification waits. The mempool now rejects transactions with nonstandard outputs, including dust or oversized OP_RETURN data, before checking scripts and proofs.

New metrics report sync restarts, block errors and the age of the oldest download. Memory metrics cover process use and recent-block data. A node that has no outbound peers or peer addresses now retries DNS seeders and configured or saved peers at most every five minutes rather than waiting for a restart.

The Foundation advises node operators, including miners and mining pools, as well as wallet, exchange and lightwalletd operators, to upgrade. Moving from 7.0.0 requires no migration or resync. Developers using Zebra’s Rust crates face breaking API changes: all library crates except tower-batch-control and tower-fallback receive a new major version.

The post says Zebra 7.1.0 is supported until around December 10, 2026, after which zebrad stops itself. Operators using the health endpoint should also note that it now serves one request per connection, closes connections that do not send request headers within five seconds and keeps at most 32 connections open.

Sources

  1. Original source Zcash Foundation - Zcash Community Forum forum.zcashcommunity.com

Related stories

Explore

More articles