The README (L57) plans an upgrade of the proxy from ThunderLoan to ThunderLoanUpgraded. That upgrade should keep all existing proxy state, so the flash-loan fee stays at 3e15 / 1e18 (0.3%) and getCalculatedFee keeps charging 0.3% of the borrowed amount's WETH value.
V1 stores s_feePrecision (set to 1e18) and s_flashLoanFee (set to 3e15) in consecutive storage slots directly after s_tokenToAssetToken. V2 removes s_feePrecision and replaces it with the constant FEE_PRECISION, which takes no storage slot. V2's s_flashLoanFee therefore lands in the slot where V1 stored s_feePrecision, and every later variable moves up one slot. After upgradeTo, getFee() returns 1e18 and getCalculatedFee charges 100% of the borrowed value. Nothing on the upgrade path corrects this: _authorizeUpgrade only checks onlyOwner, and initialize cannot run a second time.
Likelihood:
The trigger is the owner's own planned upgradeTo(ThunderLoanUpgraded), which the README announces and puts in scope. No attacker and no owner mistake are needed, and every proxy upgraded from V1 gets the wrong fee.
Neither _authorizeUpgrade (an empty onlyOwner function) nor initialize (already consumed on the proxy) checks or resets the layout, so the wrong fee is live from the upgrade transaction onward.
It is not rated High because it depends on a single privileged, one-time action, and the owner can restore the fee with updateFlashLoanFee(3e15) once the problem is noticed (the PoC confirms this). That limits how long the wrong fee stays in effect.
Impact:
The flash-loan fee goes from 3e15 to 1e18, 333 times the intended rate. getCalculatedFee on a 100e18 loan of a token priced 1:1 in WETH returns 100e18 (100%) instead of 0.3e18. Flash loans budgeted for the normal 0.3% fee revert with ThunderLoan__NotPaidBack, so the protocol's core function stops working and LP fee income stops until the owner intervenes.
Borrowers lose funds directly: a receiver that repays amount + the quoted fee from its own balance pays 100e18 instead of 0.3e18 for the same 100e18 loan.
LP principal is not lost; the inflated fee goes to LPs through the exchange rate. As side effects, getFeePrecision() no longer exists on the proxy, and the old 3e15 value is orphaned in the slot V2 uses as the s_currentlyFlashLoaning mapping base. That slot is harmless while all flags read false.
The PoC (test/PoC_TL-03.t.sol) puts ThunderLoan behind an ERC1967Proxy and initializes it. It allows a mock token priced 1:1 in WETH, deposits LP funds, and then has the legitimate owner call upgradeTo(new ThunderLoanUpgraded()). The tests assert the following:
Under V1, getFee() == 3e15, raw slot 203 == 1e18 and raw slot 204 == 3e15.
After the upgrade the storage is unchanged, but V2 getFee() == 1e18, getCalculatedFee(token, 100e18) == 100e18, and initialize reverts.
A flash loan that succeeds on V1 with a 1e18 fee buffer reverts on V2 with ThunderLoan__NotPaidBack.
A receiver that repays amount + fee pays 0.3e18 on V1 and 100e18 on V2.
The owner can restore the fee with updateFlashLoanFee(3e15).
Run it with forge test --match-path test/PoC_TL-03.t.sol -vv.
File test/PoC_TL-03.t.sol; run FOUNDRY_FFI=false forge test --match-path test/PoC_TL-03.t.sol -vv.
## Description The thunderloanupgrade.sol storage layout is not compatible with the storage layout of thunderloan.sol which will cause storage collision and mismatch of variable to different data. ## Vulnerability Details Thunderloan.sol at slot 1,2 and 3 holds s_feePrecision, s_flashLoanFee and s_currentlyFlashLoaning, respectively, but the ThunderLoanUpgraded at slot 1 and 2 holds s_flashLoanFee, s_currentlyFlashLoaning respectively. the s_feePrecision from the thunderloan.sol was changed to a constant variable which will no longer be assessed from the state variable. This will cause the location at which the upgraded version will be pointing to for some significant state variables like s_flashLoanFee to be wrong because s_flashLoanFee is now pointing to the slot of the s_feePrecision in the thunderloan.sol and when this fee is used to compute the fee for flashloan it will return a fee amount greater than the intention of the developer. s_currentlyFlashLoaning might not really be affected as it is back to default when a flashloan is completed but still to be noted that the value at that slot can be cleared to be on a safer side. ## Impact 1. Fee is miscalculated for flashloan 1. users pay same amount of what they borrowed as fee ## POC 2 ``` function testFlashLoanAfterUpgrade() public setAllowedToken hasDeposits { //upgrade thunderloan upgradeThunderloan(); uint256 amountToBorrow = AMOUNT * 10; console.log("amount flashloaned", amountToBorrow); uint256 calculatedFee = thunderLoan.getCalculatedFee( tokenA, amountToBorrow ); AssetToken assetToken = thunderLoan.getAssetFromToken(tokenA); vm.startPrank(user); tokenA.mint(address(mockFlashLoanReceiver), amountToBorrow); thunderLoan.flashloan( address(mockFlashLoanReceiver), tokenA, amountToBorrow, "" ); vm.stopPrank(); console.log("feepaid", calculatedFee); assertEq(amountToBorrow, calculatedFee); } ``` Add the code above to thunderloantest.t.sol and run `forge test --mt testFlashLoanAfterUpgrade -vv` to test for the second poc ## Recommendations The team should should make sure the the fee is pointing to the correct location as intended by the developer: a suggestion recommendation is for the team to get the feeValue from the previous implementation, clear the values that will not be needed again and after upgrade reset the fee back to its previous value from the implementation. ##POC for recommendation ``` // function upgradeThunderloanFixed() internal { thunderLoanUpgraded = new ThunderLoanUpgraded(); //getting the current fee; uint fee = thunderLoan.getFee(); // clear the fee as thunderLoan.updateFlashLoanFee(0); // upgrade to the new implementation thunderLoan.upgradeTo(address(thunderLoanUpgraded)); //wrapped the abi thunderLoanUpgraded = ThunderLoanUpgraded(address(proxy)); // set the fee back to the correct value thunderLoanUpgraded.updateFlashLoanFee(fee); } function testSlotValuesFixedfterUpgrade() public setAllowedToken { AssetToken asset = thunderLoan.getAssetFromToken(tokenA); uint precision = thunderLoan.getFeePrecision(); uint fee = thunderLoan.getFee(); bool isflanshloaning = thunderLoan.isCurrentlyFlashLoaning(tokenA); /// 4 slots before upgrade console.log("????SLOTS VALUE BEFORE UPGRADE????"); console.log("slot 0 for s_tokenToAssetToken =>", address(asset)); console.log("slot 1 for s_feePrecision =>", precision); console.log("slot 2 for s_flashLoanFee =>", fee); console.log("slot 3 for s_currentlyFlashLoaning =>", isflanshloaning); //upgrade function upgradeThunderloanFixed(); //// after upgrade they are only 3 valid slot left because precision is now set to constant AssetToken assetUpgrade = thunderLoan.getAssetFromToken(tokenA); uint feeUpgrade = thunderLoan.getFee(); bool isflanshloaningUpgrade = thunderLoan.isCurrentlyFlashLoaning( tokenA ); console.log("????SLOTS VALUE After UPGRADE????"); console.log("slot 0 for s_tokenToAssetToken =>", address(assetUpgrade)); console.log("slot 1 for s_flashLoanFee =>", feeUpgrade); console.log( "slot 2 for s_currentlyFlashLoaning =>", isflanshloaningUpgrade ); assertEq(address(asset), address(assetUpgrade)); //asserting precision value before upgrade to be what fee takes after upgrades assertEq(fee, feeUpgrade); // #POC assertEq(isflanshloaning, isflanshloaningUpgrade); } ``` Add the code above to thunderloantest.t.sol and run with `forge test --mt testSlotValuesFixedfterUpgrade -vv`. it can also be tested with `testFlashLoanAfterUpgrade function` and see the fee properly calculated for flashloan
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.