Posts tagged response_amp.

A single unauthenticated eth_simulateV1 call with a gap between two block numbers makes go-ethereum synthesise up to ~256 full block headers, expanding a ~285-byte request into a ~434 KB response.

Zebra's getaddresstxids RPC returns every transaction identifier for a queried transparent address without pagination, allowing a ~116-byte request to trigger a response that scales with the number of transactions at the address, measured at ~578× amplification in controlled testing.

Zebra's `getaddressutxos` RPC returns all UTXOs for a transparent address without pagination, allowing an attacker to amplify a ~116 B request into a ~236 KB response (≈2,033×) by seeding an address with dust UTXOs.

eth_getLogs returns every log matching a filter across the requested block span in one JSON-RPC response, so a tiny wide-range or broad-topic request forces an exposed go-ethereum node to scan the range and serialise an unbounded matched-log set — a response-amplification DoS payable by an unauthenticated caller.