DeCus
Submit a BugProgram Overview
DeCus is a decentralized and high-performance cross-chain platform dedicated to bringing Bitcoin to the DeFi ecosystem and making other blockchain assets flow freely across different chains.
For more information about DeCus, please visit https://decus.io/.
This bug bounty program is focused on their smart contracts and app and is focused on preventing:
- Loss of user funds staked (principal) by freezing or theft
- Loss of governance funds
- Smart contract fails to deliver promised returns
- Redirected funds by address modification
- Injection of text
- Users spoofing other users
- Shell access on server
Rewards by Threat Level
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.
There is one exclusion from the above Severity Classification for this bug bounty program:
- Medium Level Security - Excluded: - Griefing denial of service (i.e. attacker spends as much in gas as damage to the contract).
All web/app bug reports must come with a PoC in order to be considered for a reward. All High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible 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 listed in the Audit Report of SLOWMIST are not eligible for a reward:
- The issue of the minimum bid value
- Compatibility issue
- Access control issue
- Risk of excessive authority
- Redundant code
- Add confiscation issue
- Funds remaining after refund
- PayExtraBurnFee issue
- Malleable attack risk
- Other vulnerabilities listed in the Audit Report
Payouts are handled by the DeCus team directly and are denominated in USD. However, payouts are done in USDT or DCS, with the choice of the ratio at the discretion of the team.
Smart Contracts and Blockchain
- Critical
- Level
- Up to USD $100,000
- Payout
- high
- Level
- USD $15,000
- Payout
- medium
- Level
- USD $5,000
- Payout
- low
- Level
- USD $1,000
- Payout
Web and Apps
- Critical
- Level
- USD $10,000
- Payout
- high
- Level
- USD $2,000
- Payout
- medium
- Level
- USD $1,000
- Payout
- low
- Level
- USD $500
- Payout
Assets in Scope
All smart contracts of DeCus can be found at https://github.com/decus-io/decus-core. 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 staked (principal) by freezing or theft
- Loss of governance funds
- Smart contract fails to deliver promised returns
Web/App
- Redirected funds by address modification
- Injection of text
- Users spoofing other users
- Shell access on server
- Smart Contract - DeCus System
- Type
- Smart Contract - Keeper Registry
- Type
- Smart Contract - Keeper Reward
- Type
- https://app.decus.io
- Target
- Web/App - Main Web app
- Type
Prioritized Vulnerabilities
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)
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)
- Minting repeatedly to occupy all available Keeper groups and block system
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