ShibaNova

ShibaNova is a Decentralized Exchange and Automatic Market Maker built on the Binance Smart Chain. We aim to solve one of the fundamental problems in Decentralized Finance (DeFi), where the project’s native token rises in value at launch only to incrementally decrease in value day after day until it ultimately goes down to zero. We solve this problem by turning our investors into valued shareholders - eligible to get their share of 75% of fees collected in our dApp.

By providing liquidity to our project and creating/holding our dividend tokens, our shareholders are able to earn daily passive income. This daily dividends system not only incentivizes long-term holding but promotes ownership of the project by the entire community. This is our vision for DeFi 2.0 - sustainable, secure, successful, cross-chain, and universal.

Website: www.ShibaNova.io

Twitter: www.Twitter.com/ShibaNovaDEFI

Telegram: t.me/ShibaNovaDEX

The bug bounty program covers its smart contracts and other software and is focused on the prevention of the following negative impacts:

• Theft of funds in our yield farming pools and farms, including our Liquidity Pairs.
• Theft of funds in our marketing/expenses/and dividend Money Pot
• Leak of user data and wallet addresses
• Access to sensitive pages without authorization

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 and app bugs must come with a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected with a request for a PoC.

Critical and High smart contract vulnerabilities require a PoC and a suggestion for a fix in order to be considered for a reward.

Payouts are handled by the ShibaNova team directly and are denominated in USD. Payouts are done in BUSD, BNB, or NOVA, at the discretion of the team. Payouts may be done over a period of time at the discretion of the team.

For additional reference, further information about their smart contracts can be found here - https://github.com/ShibaNova/Contracts. However, only the smart contracts within the assets in scope table itself are considered as in-scope for 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

• Loss of user funds staked (principal) by freezing or theft
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Temporary freezing of funds for any amount of time
• Unable to call smart contract
• Smart contract gas drainage
• Smart contract fails to deliver promised returns

Web/App

• Redirected funds by address modification
• Any other direct loss of funds impact

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