RootstockLabs, previously IOVLabs, have been longstanding contributors to Rootstock, Bitcoin’s DeFi layer. Launched in 2018, Rootstock allows anyone to develop apps and services on top of the planet’s most secure and decentralized financial infrastructure; Bitcoin. Today we continue to contribute to Rootstock’s evolution by building tools and technology focused on scaling Bitcoin and making it work for everyone.
Triaged by Immunefi
PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Vector Definition
Deployment assumptions
- HSM, middleware, and Powpeg-Node run on the same host.
- HSM and middleware expose no external network interfaces (no inbound remote access paths).
- Powpeg-Node is the only externally connected component, used to sync blockchain data and forward it to the middleware, and its public exposure is limited.
Remote
“Remote” means the attacker cannot directly reach the HSM or middleware over the network and has no local access to the host. The only realistic remote reachability is indirect, via untrusted but consensus-valid on-chain data produced and propagated by the RSK network, synchronized by Powpeg-Node, and forwarded to the middleware (and subsequently to the HSM) for processing, where it may trigger vulnerable parsing/validation/logic.
Local
“Local” means the attacker has obtained root (or equivalent) control of the host running Powpeg-Node, the middleware, and the HSM (for example via shell/SSH access, a compromised account, or malware), but does not require physical access to the machine or device. With this level of access, the attacker can directly issue commands to the HSM via its local interfaces, ultimately affecting HSM operations.
Physical
“Physical” means the attacker has obtained physical access to the HSM device, enabling direct interaction and potential hardware tampering. With this level of access, the attacker may be able to probe, manipulate, reset, fault, or modify the device or its connections, potentially bypassing logical protections and ultimately affecting HSM operations.
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Remote extraction of seed or private keys
Network not being able to confirm new transactions (total network shutdown)
Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Execute arbitrary system commands
Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
Taking down the application/website
Out of scope
These impacts are out of scope for this bug bounty program.
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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- 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
Blockchain/DLT & Smart Contract Specific:
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
- Impacts requiring physical access or local user level access to a user's device.
- Impact from previously known vulnerable libraries without a working PoC.
- Rsk-powhsm:
- Impacts related to the Ledger devices used on rsksmart/rsk-powhsm; including their physical security.
- Impacts which ultimately don't allow for the arbitrary or unsecure use of the keys derived from the device seed for project rsksmart/rsk-powhsm.
- Impacts related to the TCPSigner component, which is made solely for testing and fuzzing purposes for project rsksmart/rsk-powhsm.
- Impacts related to code under the following path firmware/src/hal/src/x86/ since it’s a part of the code related to the TCPSigner component for project rsksmart/rsk-powhsm.
- Impacts related to the SGX code for project rsksmart/rsk-powhsm.
- Impacts related to DoS by physical or local access to the Ledger device.
- Impacts related to Ledger company source code will be eligible for rewards after 90 days from the initial disclosure from Ledger.
- Impacts related to Ledger company source code will be rewarded according to the general reward table specified for the bug bounty program, rather than the powHSM project reward table.
- Rskj
- Impacts related to the encryption or access control of the integrated wallet of rsksmart/rskj.
- Impacts related to the configuration option that allows storing private keys on disk.
- JSON RPC personal module and the filter API including eth_newFilter, eth_blockFilter,eth_getLogs for rsksmart/rskj.
- DoS attacks on any JSON RPC module that is not enabled by default (admin, debug, trace, etc).
- DoS or resource consumption issues are limited to nodes deployed following the official Ubuntu installation guide (https://dev.rootstock.io/node-operators/setup/installation/ubuntu), as it reflects the intended production setup with the correct system-level settings for node operators. Any DoS or resource consumption issues affecting nodes installed or configured using any other method are out of scope.
- DoS reports based solely on long-running transaction, contract, or block execution are out of scope if execution completes within RSK's expected block time (~30 seconds).
- Vulnerabilities in features that are under development and not enabled by default.
- Liquidity-bridge-contract
- contracts/Quotes.sol and contracts/LiquidityBridgeContract.sol are out-of-scope for rsksmart/liquidity-bridge-contract
Websites and Apps
- Theoretical impacts without any proof or demonstration
- Impacts involving attacks requiring physical access to the victim device
- Impacts involving attacks requiring access to the local network of the victim
- Reflected plain text injection (e.g. url parameters, path, etc.)
- This does not exclude reflected HTML injection with or without JavaScript
- This does not exclude persistent plain text injection
- Any impacts involving self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (e.g. logout CSRF)
- Impacts related to missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure, such as IPs, server names, and most stack traces
- Impacts causing only the enumeration or confirmation of the existence of users or tenants
- Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- Impacts that only require DDoS
- UX and UI impacts that do not materially disrupt use of the platform
- Impacts primarily caused by browser/plugin defects
- Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
- Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
- SPF/DMARC misconfigured records)
- Missing HTTP Headers without demonstrated impact
- Automated scanner reports without demonstrated impact
- UI/UX best practice recommendations
- Non-future-proof NFT rendering
Prohibited Activities:
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
Blockchain/DLT specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% 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