29 December 2021
Live since
No
KYC required
$100,000
Maximum bounty

Program Overview

Harmony is an open and fast blockchain. Our mainnet runs Ethereum applications with 2-second transaction finality and 1000 times lower fees. Harmony is your open platform for assets, collectibles, identity, governance. Our secure bridges offer cross-chain asset transfers with Ethereum, Binance and 3 other chains.

For more information about Harmony, please visit https://www.harmony.one/.

This bug bounty program is focused on their app and is focused on preventing:

  • Leak of user data
  • Deletion of user data
  • Redirected funds by address modification
  • Site goes down
  • Accessing sensitive pages without authorization
  • 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.

All web/app bug reports must come with a PoC in order to be considered for a reward.

This bug bounty program will also have a hard cap of USD 1 000 000. In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis. All remaining valid reports will have their rewards considered at the discretion of the team.

Payouts are handled by the Harmony team directly and are denominated in USD. However, payouts are done in ONE.

Web and Apps

Critical
Level
USD $100,000
Payout
high
Level
USD $20,000
Payout
medium
Level
USD $5,000
Payout
low
Level
USD $1,000
Payout

Assets in Scope

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.

Web/App

  • Leak of user data
  • Deletion of user data
  • Redirected funds by address modification
  • Site goes down
  • Accessing sensitive pages without authorization
  • Injection of text
  • Users spoofing other users
  • Shell access on server
Web/App - Explorer
Type
Web/App - Staking
Type
Web/App - Multisig
Type
Web/App - Gateway
Type
Web/App - Wallet
Type
Web/App - Chrome Extension
Type
App - Native Mobile App
Type
App - Native Mobile App
Type
App - Native Mobile App
Type

Prioritized Vulnerabilities

We are especially interested in receiving and rewarding vulnerabilities of the following types:

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)

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