28934 - [SC - Insight] TimelockcancelTransaction does not check asser...

Submitted on Mar 2nd 2024 at 05:15:26 UTC by @Obin for Boost | Puffer Finance

Report ID: #28934

Report type: Smart Contract

Report severity: Insight

Target: https://etherscan.io/address/0x3C28B7c7Ba1A1f55c9Ce66b263B33B204f2126eA#code

Impacts:

  • Contract accepts unqueued Tx as input leading to multiple unexpected behavior & Impacts

Description

Brief/Intro

The cancelTransaction() in Timelock .sol does not check that input is a valid queued Tx. This leads to multiple undesired scenarios / impacts. They include:

Impact Details

In a situation of input error, contract will:

  1. Not actually delete Tx as intended.

  2. Contract can wrongly emit / publish wrong data to have been cancelled. Hence deceiving the public.

  3. A reversed Decision (cancelled TX) may still go through undesirously.

POC

See below.

Mitigation

Proof of Concept

Last updated

Was this helpful?