GeroWallet

GeroWallet is an all-in-one DeFi app designed to be a powerful instrument for experienced and new users alike. GeroWallet delivers a redefined UX by focusing on a user-centric design. Our product features a built-in multi-functional toolkit that boasts inter-chain and cross-chain swapping, liquidity lock, staking, swapping, and fiat on/off ramp functionality.

For more information about GeroWallet, please visit https://gerowallet.io/.

The bug bounty program covers its Website and Chrome Extension and is focused on preventing the following impacts:

• Thefts and freezing of principal of any amount
• Theft of any funds / tokens / nfts
• Leak of seed phrase
• Manipulating the user to send funds within the wallet
• Man in the middle attacks that lead to financial loss
• XSS/CSRF with financial loss as a result
• Loss of any fiat amount when user will be using on/off ramp services

Rewards are distributed for critical vulnerabilities only, defined as vulnerabilities that lead directly to a financial loss for users.

All bug reports must come with a PoC demonstrating direct financial impact in order to be accepted.

Bug reports that do not contain a vulnerability that leads to a direct loss of funds are not accepted in this bug bounty program. Additionally, any vulnerability that involves social engineering is not in-scope.

Payouts are handled by the GeroWallet team directly and are denominated in USD. Payouts are done in $GERO.

Backend Services hosted in AWS are out of scope unless there is a vulnerability that can lead to loss of client’s funds or something equivalent.

The GeroWallet Chrome Extension is in scope. However, anything else around the Google domain is not in scope. The link is only provided as a means to access the extension.

Until August 12, 2021, access to the GeroWallet Chrome Extension (which is the second Asset link listed in the above Asset table) requires email access. In order to request access, please email chris@gerowallet.io, and access will be provided. However, all bug reports must be submitted on Immunefi.

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.

Web/App

• Thefts and freezing of principal of any amount
• Theft of any funds / tokens / nfts
• Leak of seed phrase
• Manipulating the user to send funds within the wallet
• Man in the middle attacks
• XSS/CSRF with financial loss as a result
• Loss of any fiat amount when user will be using on/off ramp services

We are especially interested in receiving and rewarding vulnerabilities of the following types. However, they are only accepted if they result in an accepted impact.

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
• 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)

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)