Liquidity Management
Gamma
DeFiFoundry
50,000 USDC
View results
Previous Next
Submission Details
Severity: low
Invalid

No checks for values below those set by admin in the GmxProxy::setMinEth function

ckcodemax

Summary

In the GmxProxy::setMinEth function, any number can be passed, even zero.

Vulnerability Details

No checks in GmxProxy::setMinEth function.

Impact

Zero can be set as the minEth

Proof of Code:

Please note that this a fork test. We need to use a fork url for arbitrum. You can get a fork url from [alchemy](https://www.alchemy.com/).

The test won't run if you do not use a fork url. To run the test, open a new terminal and run,

forge test --fork-url $YOUR_ARBITRUM_FORK_URL test/PerpetualVault.t.sol --mt testFuzzSetMinEthCanBeAnyNumber -vvv

Add the following lines of code to the test/PerpetualVault.t.sol file.

For this test to run, we need to initialize the gmxUtilsLogic as a state variable. Make these modifications to the test/PerpetualVault.t.sol

​
contract PerpetualVaultTest is Test, ArbitrumTest {
enum PROTOCOL {
DEX,
GMX
}
​
address payable vault;
address payable vault2x;
VaultReader reader;
MockData mockData;
+ GmxProxy gmxUtilsLogic;
​
function setUp() public {
//every other thing here remains thesame
+ gmxUtilsLogic = new GmxProxy();
​
}
function testFuzzSetMinEthCanBeAnyNumber(uint256 _min) external {
address owner = gmxUtilsLogic.owner();
vm.prank(owner);
gmxUtilsLogic.setMinEth(_min);
​
assertTrue(gmxUtilsLogic.minEth() >= 0.002 ether);
​
}
​

Recommendations

The issue stems from [GmxProxy::setMinEth](https://github.com/CodeHawks-Contests/2025-02-gamma/blob/84b9da452fc84762378481fa39b4087b10bab5e0/contracts/GmxProxy.sol#L359)

The solution is to add a check if the _minEth is less than 0.002 ether .

​
function setMinEth(uint256 _minEth) external onlyOwner {
+ require(_minEth >= 0.002 ether, "Cannot send below min eth");
minEth = _minEth;
}
Updates

Lead Judging Commences

n0kto Lead Judge 8 months ago
Submission Judgement Published
Invalidated
Reason: Non-acceptable severity
Assigned finding tags:

Admin is trusted / Malicious keepers

Please read the CodeHawks documentation to know which submissions are valid. If you disagree, provide a coded PoC and explain the real likelihood and the detailed impact on the mainnet without any supposition (if, it could, etc) to prove your point. Keepers are added by the admin, there is no "malicious keeper" and if there is a problem in those keepers, that's out of scope. ReadMe and known issues states: " * System relies heavily on keeper for executing trades * Single keeper point of failure if not properly distributed * Malicious keeper could potentially front-run or delay transactions * Assume that Keeper will always have enough gas to execute transactions. There is a pay execution fee function, but the assumption should be that there's more than enough gas to cover transaction failures, retries, etc * There are two spot swap functionalies: (1) using GMX swap and (2) using Paraswap. We can assume that any swap failure will be retried until success. " " * Heavy dependency on GMX protocol functioning correctly * Owner can update GMX-related addresses * Changes in GMX protocol could impact system operations * We can assume that the GMX keeper won't misbehave, delay, or go offline. " "Issues related to GMX Keepers being DOS'd or losing functionality would be considered invalid."

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.