Hedera is a fully open source, proof-of-stake, public network and governing body for building and deploying decentralized applications. It offers developers three primary services: Solidity-based smart contracts, consensus, and token services. Hedera is unique in that it is incredibly fast, energy-efficient (carbon negative), and secure — these advantages can be attributed to its underlying hashgraph consensus algorithm.
Triaged by Immunefi
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Suggestions for places to start
- Ability to execute system commands
- Signing transactions for other users
- Redirection of user deposits and withdrawals
- Tamper/manipulate Hashgraph history to invalidate transactions
- Tampering with submitted transactions
- Authorizing transactions without approval from the required signers/owners
- Preventing network from reaching consensus on transactions that are submitted
- Preventing gossip of a transaction or multiple transactions
- Bugs that cause the in-scope service to crash (e.g., Non-network-based DoS)
- Remote code execution vulnerabilities
- Attacks that cause a probabilistic consensus failure; or a deterministic consensus failure in reconnected nodes
- Effective non-network-bandwidth-flooding DDoS attacks (e.g., transaction hammering)
- Malicious capabilities of Hedera Token Service functions exposed via System contracts (e.g. transferring assets out of an account without permissions).
- System Smart contract modifiers not respected
- Bugs in the economic system to defraud other participants (e.g. avoid transaction fees to full nodes)
- Prevent node from accessing the network
- Incorrect or missing records exported to mirror nodes
- Correct transaction fees not being applied
- Unauthorized Hedera Token Service (HTS) activity
- Overpayment or underpayment of staking rewards
- Theft of unpaid staking rewards
- Sensitive information leakage (e.g., private keys, wallets credentials etc). Public keys are excluded from this scope
Network not being able to confirm new transactions (total network shutdown)
Network partition caused outside of design parameters
Direct loss of funds
Unintended permanent freezing of funds
Any impact caused by Tampering/Manipulating Hashgraph history
Temporary freezing of network transactions by delaying one block by 500% or more of the average block time of the preceding 24 hours beyond standard difficulty adjustments
Preventing gossip of a transaction or multiple transactions
Reorganizing transaction history without direct theft of funds
Any impacts caused by Tampering with submitted transactions
Authorizing transactions without approval from signers/owners
Non-network-based DoS affecting projects with greater than or equal to 25% of the market capitalization on top of the respective layer
Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours
Out of scope
Blockchain/DLT
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 2/3 attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers