Platform: Code4rena
Start Date: 01/05/2024
Pot Size: $12,100 USDC
Total HM: 1
Participants: 47
Period: 7 days
Judge: Koolex
Id: 371
League: ETH
Rank: 10/47
Findings: 1
Award: $386.08
🌟 Selected for report: 0
🚀 Solo Findings: 0
🌟 Selected for report: 0xnev
Also found by: 0x04bytes, 0xBugSlayer, 0xJoyBoy03, 0xSecuri, 0xrex, Bigsam, DMoore, Evo, Greed, Kirkeelee, Krace, Pechenite, Rhaydden, SBSecurity, Sajjad, TheFabled, Topmark, XDZIBECX, ZanyBonzy, _karanel, bbl4de, btk, d3e4, gumgumzum, nfmelendez, novamanbg, petarP1998, samuraii77, sandy, shaflow2, sldtyenj12, web3er, y4y, yovchev_yoan
284.4444 USDC - $284.44
The Prelaunch Points system will lock fund of the users for at least
7 days after the authorized owner of the smart contract set
the lpETH
via setLoopAddresses()
function. Within that period,
the users can withdraw their fund. If the users withdraw their
fund, they can't claim lpETH
anymore. But this mechanism can be manipulated
by only locking small amount of wrapped LRT
and then send the rest of
the fund (in the form of ethers) at the time the users claim the lpETH
.
Within the locking and before claim period, the users can use the rest of
their fund to do something else.
User locks small amount of wrapped LRT
. When the claim date comes,
before calling claim()
function, the user sends ethers to the contract.
When the claim()
function is called, all of its balance will be converted into
lpETH
(including the ethers sent by the user).
Now the user has lpETH
from conversion of the amount of locked wrapped LRT
plus the
amount of ethers sent.
The user can manipulate locking mechanism by locking a small amount of wrapped LRT
and provide the rest of the ethers at the claim date to get lpETH
.
Manual Review
Only deposit the amount of ethers bought from exchange when user uses wrapped LRT
in order to claim lpETH
.
Other
#0 - c4-judge
2024-05-15T14:19:38Z
koolexcrypto marked the issue as duplicate of #6
#1 - c4-judge
2024-05-31T09:58:28Z
koolexcrypto marked the issue as duplicate of #33
#2 - c4-judge
2024-06-05T09:55:53Z
koolexcrypto changed the severity to 3 (High Risk)
#3 - c4-judge
2024-06-05T09:56:17Z
koolexcrypto marked the issue as satisfactory