Bytecode verification
Summary
The Perpetual Vault Protocol does not implement address bytecode verification, which could lead to potential risks when interacting with external contracts.
Vulnerability Details
The GmxProxy and PerpetualVault contracts do not verify the bytecode of external contracts before interacting with them. This could allow an attacker to deploy a malicious contract with the same address as a legitimate one on a different chain or network.
Impact
Interacting with a malicious contract could lead to unexpected behavior, financial losses, or security breaches.
Tools Used
Manual code review
Recommendations
Implement bytecode verification for external contracts to ensure they are the expected contracts. This could involve checking the contract's address against a known, trusted address or using a trusted registry.
Lead Judging Commences
Informational or Gas
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.
Prize pool breakdown
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.