tx.origin
is being used in contract GmxProxy.sol
but it is advisable not to use tx.origin
for main access control functions.
Code:
Also it can lead to a bug if someone detects GMXproxy is deployed but vault is not set and runs it before Perpetual vault deployment
Many DeFi owners operate through Multisigs or Account Abstraction wallets, where tx.origin
does not reliably represent the actual end user.
Manual Review
Better to use msg.sender or use owner variable for passing from Perpetual vault contract to GMXproxy contract and replace tx.origin with msg.sender/owner in this contract
Lightchaser: Medium-5
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.