31149 - [SC - Critical] Manipulation of governance voting result by unl...
Manipulation of governance voting result by unlimited minting the Flux Token by repeatly call poke function
Submitted on May 13th 2024 at 16:06:32 UTC by @perseverance for Boost | Alchemix
Report ID: #31149
Report type: Smart Contract
Report severity: Critical
Target: https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/FluxToken.sol
Impacts:
Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results
Description
Description
Brief/Intro
Flux token implements a standard ERC20 token with extra features. Flux tokens are accrued by users of VotingEscrow when voting in the contract Voter. Flux tokens can be used to: i) exit a ve-position early by paying a penalty fee when calling function startCooldown, ii) boost voting power of a NFT holder in contract Voter, or iii) as a normal ERC20 token that can be traded in other systems.
So Flux tokens can be used to boost the voting power of a NFT holder. It is shown in the code of vote() function as below.
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/Voter.sol#L228C5-L233C6
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/Voter.sol#L412-L455
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/FluxToken.sol#L195-L199
So users can boost the voting power up to unclaimedFlux of the tokenId.
The unclaimedFlux[_tokenId] is updated in the function accrueFlux()
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/FluxToken.sol#L188C5-L192C6
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/VotingEscrow.sol#L377-L385
So according to the design of the Alchemix DAO system, if an user have a locked tokenID then with balanceA then the user can get maximum Fluxtoken for 1 epoch is
The vulnerability
Vulnerability Details
Now an attacker can mint unlimited times of the amount of Flux Token for 1 epoch intended by the Alchemix DAO system by the using the same amount of capital.
So if an user have locked 10 * 10 ** 18 BPT token for 2 weeks, then the maximal amount of flux tokens can be claimed in 1 epoch is:
270057394723366387 = 270_057_394_723_366_387 = 270 e15 Flux token.
This amount here is just an example.
Attacker can manipulate the system to mint unlimited times of Flux token by exploiting the function poke() in Voter contract.
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/Voter.sol#L195-L212
This function call will call _vote() internal function then call accrueFlux function of contract FluxToken
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/Voter.sol#L412-L423
Since the attacker is the owner of tokenId so this is normal. This call will call accrueFlux function to update the unclaimedFlux for the tokenId.
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/FluxToken.sol#L188C5-L192C6
Now this tokenId1 has the balanceTokenId1 => unclaimedFlux[_tokenId] += amount
Since the poke() function allows the owner of the tokenId to call this function unlimited times during the same EPOCH. Every time the poke() function is called, then the unclaimedFlux is added one more time.
By repeatedly call poke() function, the attacker will get more Flux token unlimited times of the current intended amount. When have more flux token, the attacker can use it as boost to manipulate the system to manipulate governance.
Impacts
About the severity assessment
The impact is that the attacker will be able to exploit the system to get unlimited times bigger Flux token for the same capital.
Since the Flux tokens can be used to boost the Voting power in Vote function and can manipulate the governance voting result. The attacker can also mint Flux token to get benefit as the Flux token can be traded for other assets as stated by the protocol document.
The severity: Critial
Category:
Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results
Unauthorized or malicious minting of Flux token
Capital for the attack: Gas to execute the transactions. Amount of BPT can be small just to create lock position.
Easy to exploit and easy to be automated.
Please note that this bug is different from bug: Report 39030 (https://bugs.immunefi.com/dashboard/submission/39030) was reported by me. Because the bug 39030 describes the exploit using poke() and merge() function. The attack there is more complex and related to merge() functionality. For bug 39030, the attacker can mint only several times of the amount of Flux token.
This bug involves only exploit of poke() function. For this bug the attacker can mint unlimited amount of Flux token.
Proof of concept
Proof of concept
testFluxAccrual_Poke_Hacked()
I created the POC for exploit scenario
The POC code:
In this POC, I use 10 * 10**18 BPT token. The attacker create 10 tokenIds and repeately call poke(tokenId) and merge
The log shows:
So at the end of the attack: the attacker still have a tokenId with amount: 10000000000000000000 = 10 ** 18 Lock duration: 2 weeks.
So the attacker still can withdraw his capital of BPT token as normal.
The unclaimedFlux of tokenId1: 2970631341957030257000
testFluxAccrual_Poke_Normal()
I also created the normal scenario where a user lock 10 ** 10**18 BPT token.
The log of this test case shows:
So the unclaimedFlux1 of the tokenID1 is 270057394723366387
To compare, the attacker get 11_000 times bigger that is the number of loops. So attackers can repeat this and get the unlimited token of Flux token.
So attacker can use the gained Flux token to boost the voting power. In this POC, I demonstrated that the attacker can mint Flux token.
Full POC Code:
To run the test Copy the test code into the file:
https://github.com/alchemix-finance/alchemix-v2-dao/blob/main/src/test/VotingEscrow.t.sol
and run the test command for the function in the alchemix-v2-dao folder:
Logs
The full log: https://drive.google.com/file/d/1rVgRlD_C4NYKynFeBBv-YcVG8G90q-Fc/view?usp=sharing
The full log file with debug:
https://drive.google.com/file/d/1BGhCmiM-gADnQcNgvfbnDVhbDrs7oIAN/view?usp=sharing
Last updated
Was this helpful?