Lucene search
+L

4 matches found

Code423n4
Code423n4
added 2022/01/19 12:0 a.m.10 views

Incorrect params in migrateETH leads to function not working

Handle harleythedog Vulnerability details Impact In L1Migrator.sol, the function migrateETH first withdraws eth from the BridgeMinter, and then intends to send all of this eth from L1 to L2. However, the parameters are incorrectly passed to the sendTxToL2 function, so none of this withdrawn eth...

6.9AI score
SaveExploits0
Code423n4
Code423n4
added 2022/01/19 12:0 a.m.8 views

Anyone can freeze fund in BridgeMinter

Handle gzeon Vulnerability details Impact Anyone can call migrateETH and migrateLPT in L1Migrator with arbitrary maxSubmissionCost. For example when migrateLPT is called, it would withdraw all LPT from bridgeMinter, and then create a L2 retryable ticket to call the L2Migrator using...

6.9AI score
SaveExploits0
Code423n4
Code423n4
added 2022/01/19 12:0 a.m.8 views

migrateETH will not work

Handle gzeon Vulnerability details Impact migrateETH does not send the withdrawn ETH to L2 causing fund to stuck in the L1Migrator contract. Proof of Concept When migrateETH is called, it would withdraw all ETH from bridgeMinter, and then use sendTxToL2 create a L2 retryable ticket to call the...

6.8AI score
SaveExploits0
Code423n4
Code423n4
added 2022/01/16 12:0 a.m.11 views

L1Migrator.migrateETH can be used to take away protocol's access to funds

Handle Ruhum Vulnerability details Impact The L1Migrator.migrateETH function can be called by anyone. It pulls all the ETH from the BridgeMinter contract and starts the process of moving the funds to L2. First of all, this function is only executable once. The RetryableTicket created with the fir...

6.7AI score
SaveExploits0
Rows per page
Query Builder