Gear Protocol: Program info

GENERAL

The following vulnerabilities are not eligible for a reward:

• https://github.com/gear-tech/gear/issues

• Issues that cannot be reproduced on networks configured and currently run by Gear, (i.e.: Vara Network Testnet, Vara Network). Severity of issues that point out problems with the code and can theoretically affect the above network list will be considered individually.

Gear requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward.

IN SCOPE VULNERABILITIES

Gear Assets in scope table are specified to commit 22dfb9e43fe4fc608c747ca02e0e4ba7c5ccf123. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Gear that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

Critical

• Network not being able to confirm new transactions (total network shutdown)
• Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
• Permanent freezing of funds (fix requires hardfork)

High

• Unintended chain split (network partition)
• Transient consensus failures
• Network unable to process internal message queue and requires maintenance mode to restart it
• Direct loss of funds without your willing or activities: signing something etc.

Medium

• High compute consumption by validator/mining nodes when blocks are not full
• Attacks against thin clients
• DoS of greater than 30% of validator or miner nodes and does not shut down the network
• RPC API crash

Low

• DoS of greater than 10% but less than 30% of validator or miner nodes and does not shut down the network

OUT OF SCOPE VULNERABILITIES

• Issues that can be reproduced ONLY on test networks run by Gear, I.e.: Vara Network Testnet

• Severity of Issues that point out problems with the code and can theoretically affect the above network list will be considered individually.

• 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

• 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

• All bounty submissions must be accompanied by a Proof-of-Concept (PoC).
• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• Don’t spam forms or account creation flows using automated scanners
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
• Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
• 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 that are executed against project assets

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
• No vulnerability disclosure, including partial is allowed for the moment.
• Please do NOT publish/discuss bugs

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• Also, please note that if something is only possible on a testnet, the reward will be considered individually.
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps