31 May 2022
Live since
No
KYC required
$100,000
Maximum bounty

Program Overview

H2O is the first non-pegged stable asset for the Web3 Data Economy which serves as a medium of exchange and unit of account in data marketplaces. H2O is based on the RAI stable asset by Reflexer Labs. Like RAI, H2O is decentralized, permissionless and aims to minimize governance.

For more information about H2odata, please visit https://app.h2odata.xyz/#/.

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.1. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All Medium, High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required. Reports that don't explain or demonstrate the impact will not be considered.

The following vulnerabilities are not 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.

Payouts are handled by the H2odata team directly and are denominated in USD. However, payouts are done in PSDN and USDC, with the choice of the ratio at the discretion of the team.

Smart Contract

Critical
Level
Up to USD $100,000
Payout
PoC Required
High
Level
USD $30,000
Payout
PoC Required
Medium
Level
USD $10,000
Payout
PoC Required
Low
Level
USD $2,000
Payout

Websites and Applications

Critical
Level
USD $10,000
Payout
PoC Required
High
Level
USD $5,000
Payout
PoC Required
Medium
Level
USD $2,000
Payout
PoC Required

Assets in scope

All smart contracts of H2odata can be found at https://github.com/h2odata. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by H2odata that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This only applies to “Critical” impacts.

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 Contract

  • Loss of at least USD $100 000 of user funds staked (principal) by freezing or theft
    Critical
    Impact
  • Theft of unclaimed yield
    High
    Impact
  • Loss of at least USD $30 000 of user funds staked (principal) by freezing or theft
    High
    Impact
  • Permanent freezing of unclaimed yield
    High
    Impact
  • Temporary freezing of funds for a minimum of 24 hours
    High
    Impact
  • Loss of at least USD $5 000 of user funds staked (principal) by freezing or theft
    Medium
    Impact
  • Smart contract fails to deliver promised returns, but doesn’t lose value
    Low
    Impact

Websites and Applications

  • Execute arbitrary commands on production servers
    Critical
    Impact
  • Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)
    Critical
    Impact
  • Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user such as changing registration information, making trades, withdrawals resulting in loss of user funds
    Critical
    Impact
  • Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions
    Critical
    Impact
  • Injection attacks (excluding html injection attacks) such as XSS (all of them) and SQL injections,, replacing existing text with arbitrary text, arbitrary file uploads, etc.
    High
    Impact
  • H2o production’s Subdomain takeover with already-connected wallet interaction
    High
    Impact
  • Improperly disclosing confidential user information such as email address, phone number, physical address, etc.
    High
    Impact
  • Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.
    Medium
    Impact
  • HTML Injection attacks
    Medium
    Impact
  • Open Redirect in H2O production’s environment
    Medium
    Impact
  • Subdomain takeover with already-connected wallet interaction
    Medium
    Impact

Out of Scope & Rules

There are some things we explicitly ask you not to do:

  • When experimenting, please only attack accounts belonging to you. Do not use leaked or compromised accounts belonging to other users. Vulnerabilities that were discovered using leaked or compromised accounts will be disqualified.
  • Do not run automated scans without checking with us first. They are often very noisy.
  • Do not test using social engineering techniques (phishing, vishing, et.c.)
  • Do not perform DoS or DDoS attacks.
  • In any way, attack our end users, or engage in trade of stolen user credentials.

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
  • Attacks requiring physical access to the victim device
  • Attacks requiring access to the local network of the victim
  • Reflected plain text injection ex: url parameters, path, etc.
    • This does not exclude reflected HTML injection with or without javascript
    • This does not exclude persistent plain text injection
  • Self-XSS
  • Captcha bypass using OCR without impact demonstration
  • CSRF with no state modifying security impact (ex: logout CSRF)
  • 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
  • Vulnerabilities used only to enumerate or confirm the existence of users or tenants
  • Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
  • Lack of SSL/TLS best practices
  • DDoS vulnerabilities
  • Feature requests
  • Issues related to the frontend without concrete impact and PoC
  • Best practices issues without concrete impact and PoC
  • Vulnerabilities primarily caused by browser/plugin defects
  • Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
  • Any vulnerability exploit requiring browser bugs for exploitation. ex: - CSP bypass
  • Clickjacking
  • Descriptive Error Messages
  • Fingerprinting/Banner disclosure on common public services
  • HTTP Methods
  • SSL Attacks, such as BEAST/BREACH
  • Subdomain takeovers without a complete proof of concept
  • Content spoofing and text injection issues without showing an attack vector or without being able to modify HTML
  • Bugs requiring exceedingly unlikely user interaction (e.g., requiring a user to manually type in an XSS payload)
  • Vulnerabilities related to networking protocols or industry standards not controlled by H2O, including flaws that impact outdated browsers and plugins

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