The update_price function allows same-block updates to fix bad blockhashes, but this permits replaying parameters within the same block if the verifier allows it. This is partially mitigated by verifier trust but lacks additional safeguards.
The vulnerable code is in update_price:
vyper
Replay Window: Same _block_number can overwrite prior updates.
Intent: Docs note this is for fixing bad blockhashes.
PoC
Objective
Replay parameters in the same block to overwrite a legitimate update.
Prerequisites
PRICE_PARAMETERS_VERIFIER role.
Deployed scrvUSD oracle and a mock verifier allowing same-block updates.
Exploit Scenario
An attacker submits a legitimate update, then overwrites it with skewed parameters in the same block.
Proof of Concept Steps
Setup: Deploy the oracle and verifier.
Exploit Contract:
solidity
Execution:
Call exploit() in one transaction (same block).
Second call overwrites the first due to <= check.
Result: Price reflects badParams, inflating scrvUSD value.
Outcome
Shows how same-block replays can manipulate pricing, relying on verifier weakness.
Parameter Overwrite: Malicious updates could override legitimate ones, mispricing scrvUSD.
Pool Risk: Temporary mispricing could be exploited before correction.
Manual Review
Require strictly increasing block numbers or add a nonce:
vyper
- Anything related to the output by the `BLOCK_HASH_ORACLE` is OOS per \[docs here]\(<https://github.com/CodeHawks-Contests/2025-03-curve?tab=readme-ov-file#blockhash-oracle>). - The PoC utilizes a mock `BLOCK_HASH_ORACLE`which is not representative of the one used by the protocol - Even when block hash returned is incorrect, the assumption is already explicitly made known in the docs, and the contract allows a subsequent update within the same block to update and correct prices - All state roots and proofs must be verified by the OOS `StateProofVerifier` inherited as `Verifier`, so there is no proof that manipulating block timestamp/block number/inputs can affect a price update - There seems to be a lot of confusion on the block hash check. The block hash check is a unique identifier of a block and has nothing to do with the state root. All value verifications is performed by the OOS Verifier contract as mentioned above
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.