08 January 2022
Live since
Yes
KYC required
$50,000
Maximum bounty

Program Overview

Kadena was founded on the idea that blockchain could revolutionize how the world interacts and transacts. But to get to mass adoption, chain technology and the ecosystem connecting it to the business world needed to be reimagined from the ground up. Our founders built a proprietary chain architecture and created the tools to make blockchain work for business – at speed, scale, and energy efficiency previously thought unachievable.

For more information about Kadena, please visit https://kadena.io/.

This bug bounty program is focused on their smart contracts, blockchain, websites and application and is focused on preventing:

  • Network Shutdown
  • Website goes down
  • DoS attacks on node software

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.

All web/app bug reports must come with a PoC in order to be considered for a reward. All Medium, High and Critical Smart Contract bug reports require a PoC to be eligible for a reward.

The following vulnerabilities are not eligible for a reward:

  • Congestion and scalability vulnerabilities

Payouts are handled by the Kadena team directly and are denominated in USD. However, payouts are done in KDA and stablecoins, with the choice of the ratio at the discretion of the team. In addition, as part of claiming a bug bounty, whitehats must complete a KYC process by creating an account on Coinmetro.

Smart Contracts and Blockchain

Critical
Level
USD $50,000
Payout
high
Level
USD $10,000
Payout
medium
Level
USD $1,000
Payout

Web and Apps

Critical
Level
USD $50,000
Payout
high
Level
USD $10,000
Payout
medium
Level
USD $1,000
Payout

Assets in Scope

All smart contracts of Kadena can be found at https://github.com/kadena-io. 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.

Blockchain

  • DOS attacks directed at our network (eg nodes)
  • Network shut down (Critical)
  • Vulnerabilities in REST API endpoints

Smart Contracts

Any vulnerability resulting in an impact that falls under Critical, High, or Medium, according to the severity classification system

Chainweb (Blockchain) Exploits:

API specification: https://api.chainweb.com/openapi/

Exploits via the service API:

  • Crashing nodes via the service API endpoints (low to medium)

Exploits via P2P API requests:

  • Crashing individual nodes (medium to high)
  • Crashing a larger number of independent nodes (high)
  • Preventing individual nodes from processing new valid blocks (medium)
  • Preventing a larger number independent nodes from processing new valid blocks (high)
  • Causing lasting (longer than several minutes) network partitions (high)
  • Causing forks in the network that are supported by a larger number of independent nodes that persist longer than just a few dozen block in depths (high)
  • Causing permanent network forks of a larger number (>25%) of independent nodes in the network (critical)
  • Permanently preventing nodes from processing any transactions (medium)
  • Permanently preventing mining nodes from including transactions into blocks (medium)
  • Preventing particular txs from being included into blocks (low)
  • Manipulating the content of the Pact (sqlite) database of a node such that those are not consistent with block validation results (Critical)
  • Deleting (or partially deleting) the Pact (sqlite) data of a node (high)
  • Manipulating the content of the chain database (rocksdb) of a node (high)
  • Deleting (or partially deleting) the content of the chain database (rocksdb) of a node (high)

Web/App

  • Site goes down
  • Redirected funds by address modification
  • Leak of private keys

Prioritized Vulnerabilities

Refer to Impacts in Scope section above.

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
  • Centralization risks

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