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

There is no check for the minimum lock time in PerpetualVault::setLockTime.

ckcodemax

Summary

In the PerpetualVault::setLockTime, there is no check if the_lockTime is less than the minimum lock time specified in the readme, which is 1 day.

Vulnerability Details

A malicious owner may set the PerpetualVault::lockTime to any number, even 0.

Impact

Users can deposit and withdraw immediately.

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 testFuzzLockTimeCanBeLessThanADay -vvv

Add the following lines of code to the test/PerpetualVault.t.sol file. This fuzz test will revert because one or more of these conditions won't be met after a few runs.

function testFuzzLockTimeCanBeLessThanADay(uint256 lockTime) public {
uint256 minLockTime = 1 days;
address owner = PerpetualVault(vault).owner();
vm.startPrank(owner);
PerpetualVault(vault).setLockTime(lockTime);
uint256 newLockTime = PerpetualVault(vault).lockTime();
vm.stopPrank();
​
assert(newLockTime != 0);
assert(newLockTime > minLockTime);
}

Recommendations

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

The solution is to add a check for min and max values.

​
//declare the values restrictions as state variables
+ uint256 public constant minLockTime = 1 days;
​
function setLockTime(uint256 _lockTime) external onlyOwner {
+ require(_lockTime >= minLockTime, "Locktime cannot be less than a day");
lockTime = _lockTime;
}
Updates

Lead Judging Commences

n0kto Lead Judge 9 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."

n0kto Lead Judge 9 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.

Give us feedback!