What Is a “Read-Only” Reentrancy Attack?

A read-only reentrancy attack is a more subtle form where the attacker does not steal funds but instead exploits a contract's reliance on the victim contract's state during a transaction. The attacker calls the victim contract, which then calls an external contract.

This external contract calls back to the victim, but only to read a state variable (like a balance) that has not yet been updated by the current transaction. This allows the attacker to make decisions based on stale, incorrect data, potentially leading to unfair liquidations or incorrect price calculations.

How Does a Reentrancy Attack Specifically Exploit Smart Contract Logic?
Give an Example of a State Variable in a Smart Contract Used for Collateralized Lending
In an Options Contract, What State Changes Occur upon Exercise?
Can This Attack Be Prevented by Using a Non-Reentrant Lock?
Why Is Updating State before an External Call the Critical Part of the CEI Pattern?
What Role Does the CALL Opcode Play in Enabling Reentrancy?
What Is a ‘Reentrancy Attack’ and How Does It Exploit Smart Contract Logic?
What Is a Reentrancy Attack in Smart Contract Security?

Glossar