GMX

GMX is a decentralized spot and perpetual exchange that supports low swap fees and zero price impact trades.

Trading is supported by a unique multi-asset pool that earns liquidity providers fees from market making, swap fees, leverage trading (spreads, funding fees & liquidations) and asset rebalancing.

For more information about GMX, please visit https://gmx.io/.

This bug bounty program is focused on their smart contracts and app and is focused on preventing:

• Loss of user funds by freezing, theft, or manipulation of the price of GLP
• Theft or freezing of unclaimed yield
• Unable to call smart contract
• There is currently a cooldown duration of 15 minutes between minting and redeeming GLP to reduce manipulation risks, we are planning to set this duration to zero eventually, so we would want to know about potential exploits if the duration is zero
• There is a minimum price movement of 1.5% required for positions to be in profit, this is to mitigate front-running issues, we would want to know about potential exploits if this threshold is reduced to e.g. 0.5%
• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Temporary freezing of fund for any amount of time
• Leak of user data
• Deletion of user data
• Redirected funds by address modification
• Site goes down
• Accessing sensitive pages without authorization
• Injection of text
• Users spoofing other users
• Shell access on server

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web/app bug reports must come with a PoC in order to be considered for a reward.

Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 50 000.

The following vulnerabilities are not eligible for a reward:

• Exploits that require access to the Timelock admin keys or Fast Price Feed admin keys
• Vesting schedules might be slightly faster for multiple deposits
• Vault.includeAmmPrice and Vault.useSwapPricing are not reset to default values for certain cases, these variables will not be used
• Vault.liquidatePosition does not pay the transaction sender for certain cases, this is intentional
• Exploits that are not economically practical to execute
• Exploits due to delays of price feed updates
• Calling Vault.setTokenConfig, Vault.clearTokenConfig, Vault.setTokenConfig on the same token would lead to double counting of the token amounts in GlpManager, Vault.clearTokenConfig will not be used
• GlpManager.getAum may return a slightly higher value until a liquidation occurs
• GlpManager.getAum may return a slightly lower value when there are shorts in profit but the price movement is below the 1.5% threshold
• It is possible for a user to burn and then mint GLP to frontrun price movements, the fees are assumed to be sufficient to prevent this from being profitable
• There will be some deviation of Vault.globalShortAveragePrices from the true average price if users increase their short position while the mark price is within 1.5% of their position’s average price, it is evaluated to not be economical for users to do this intentionally whether in combination with GLP minting or otherwise, GlpManager.setAumAdjustment can be used to correct this drift if required
• Vault.CollectSwapFees(_token, feeAmount, tokenToUsdMin(_token, feeAmount)) has a mixed up ordering for feeTokens and feeUsd
• It is expected that liquidators and order executors validate transactions will succeed before sending them

Payouts are handled by the GMX team directly and are denominated in USD. However, payouts are done in ETH.

All smart contracts of GMX can be found at https://github.com/gmx-io/gmx-contracts. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts/Blockchain

• Loss of user funds by freezing, theft, or manipulation of the price of GLP
• Unable to call smart contract
• There is currently a cooldown duration of 15 minutes between minting and redeeming GLP to reduce manipulation risks, we are planning to set this duration to zero eventually, so we would want to know about potential exploits if the duration is zero
• There is a minimum price movement of 1.5% required for positions to be in profit, this is to mitigate front-running issues, we would want to know about potential exploits if this threshold is reduced to e.g. 0.5%
• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Temporary freezing of fund for any amount of time
• Theft of governance funds
• Governance activity disruption

Web/App

• Leak of user data
• Deletion of user data
• Redirected funds by address modification
• Site goes down
• Accessing sensitive pages without authorization
• Injection of text
• Users spoofing other users
• Shell access on server

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• Any testing with pricing oracles or third party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty