Bogged Finance
Submit a BugProgram Overview
Bogged Finance is a set of tools that make it easy for users to trade tokens on Binance Smart Chain. We allow users to view real time charts, wallet data and Pair Information. Hundreds of thousands of users daily trust Bogged Finance for accurate, reliable information while they’re trading.
For more information about Bogged Finance, please visit https://www.bogged.finance/.
This bug bounty program is focused on their smart contracts and app and is focused on preventing:
- Thefts and freezing of principal of any amount
- Thefts and freezing of unclaimed yield of any amount
- Theft of governance funds
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. 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. All Critical Smart Contract bug reports require a PoC to be eligible for a reward.
Payouts are handled by the Bogged Finance team directly and are denominated in USD. However, payouts are done in BUSD, BNB BOG or BTC.
Smart Contract
- Critical
- Level
- USD $50,000
- Payout
- High
- Level
- USD $15,000
- Payout
- Medium
- Level
- USD $5,000
- Payout
Websites and Applications
- Critical
- Level
- USD $15,000
- Payout
Assets in scope
- Smart Contract - Router V2Type
- Smart Contract - Comp StakingType
- Smart Contract - Solo stakingType
- Smart Contract - LP stakingType
- Websites and ApplicationsType
All smart contracts of Bogged Finance can be found at https://github.com/BoggedFinance/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 Contract
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Protocol InsolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Temporary freezing of fundsHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
Websites and Applications
- Ability to execute system commandsCriticalImpact
- Extract Sensitive data/files from the server such as /etc/passwdCriticalImpact
- Taking Down the application/websiteCriticalImpact
- Stealing User CookiesCriticalImpact
- Bypassing AuthenticationCriticalImpact
- Signing transactions for other usersCriticalImpact
- Redirection of user deposits and withdrawalsCriticalImpact
- Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)CriticalImpact
- Wallet interaction modification resulting in financial lossCriticalImpact
- Direct theft of user fundsCriticalImpact
- Tampering with transactions submitted to the user’s walletCriticalImpact
- Submitting malicious transactions to an already-connected walletCriticalImpact
Out of Scope & Rules
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
- 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