GMX
GMX is a decentralized spot and perpetual exchange that supports low swap fees and zero price impact trades.
Triaged by Immunefi
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Subdomain takeover with already-connected wallet interaction
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
Direct theft of user funds
Loss of user funds by freezing, theft, or manipulation of the price of GLP
Execute arbitrary system commands
Malicious interactions with an already-connected wallet, such as:
- Modifying transaction arguments or parameters
- Substituting contract addresses
- Submitting malicious transactions
Taking down the application/website
Theft of governance funds
Redirected funds by address modification
Out of scope
Smart Contracts and Blockchain
- Best practice critiques
- If the GLP pool has a high utilization not all GLP tokens will be immediately redeemable, the borrowing fee should increase in this case and is considered regular operation
- Denial of service attacks are out of scope if the attack can be bypassed, for example, an attacker can front-run a user proposal with identical parameters to ProtocolGovernor, this can be bypassed by ending the proposal with #proposer=0x…, these kinds of attacks are out of scope
Websites and Apps
- Attacks requiring privileged access from within the organization
- Feature requests
- Best practices
- Vulnerabilities primarily caused by browser/plugin defects
- Any vulnerability exploit requiring CSP bypass resulting from a browser bug
- Vulnerabilities that require compromise of the user’s machine / browser
- Community-developed applications such as those on the ecosystem page
- Clickjacking Vulnerabilities
- Denial of service attacks on services used by the interface will be given a low classification unless the attack prevents trading or withdrawal of liquidity using the interface
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers
16 reports