Polygon

Polygon provides the core components and tools to join the new, borderless economy and society. Polygon is a decentralised Ethereum scaling platform that enables developers to build scalable user-friendly dApps with low transaction fees without ever sacrificing on security.

For more information about Polygon, please visit https://polygon.technology/.

This bug bounty program is focused on their smart contracts and apps, with the intent of preventing the following impacts:

• Loss of user funds by permanent freezing or direct theft
• Loss of governance funds
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Temporary freezing of funds for any amount of time
• Unable to call smart contract
• Network shutdown
• Smart contract gas drainage
• Smart contract fails to deliver promised returns
• Checkpoint manipulation
• Protection of Delegated and Staked Amount on Smart Contract
• Securing Bridge Transfers (Minting, Withdrawal)
• Double spend by getting the clients to accept a different chain
• Double spend by validating malicious blocks
• Tamper/manipulate blockchain history to invalidate transactions
• Cause a user to mint tokens to own account
• Undermine consensus mechanism to split the chain
• Censorship (e.g. on checkpoints)
• Steal tokens from node
• Prevent node from accessing the network
• Abuse bugs in the economic system to defraud other participants (e.g. avoid transaction fees to full nodes)
• Denial of service attacks
• Chain halt and shutting down the network

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System v2.2. 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. However, please refer to the Impacts in Scope section for a more accurate classification of impacts as well as the impacts that are accepted within the program.

A PoC and a suggestion for a fix is required for all bug reports. A high-quality suggestion for a fix may come with a bonus from the Polygon team.

All bug reports must include the following information in order to be considered for a reward:

Summary:

• add summary of the vulnerability

Steps To Reproduce:

• add details for how we can reproduce the issue

1. add step
2. add step
3. add step

Supporting Material/References:

• list any additional material (e.g. screenshots, logs, etc.)
  • attachment / reference

Bug reports containing the following will not be eligible for a reward with this bug bounty program:

• Previously known vulnerabilities (resolved or not) on the Ethereum network (and any other fork of these).
• Previously known vulnerabilities in Tendermint and or/any other fork of these.
• Previously known vulnerabilities in cosmos-sdk and or/any other fork of these.
• Previously known vulnerable libraries without a working Proof of Concept.
• Attacks requiring MITM or physical access to a user's device.
• Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.

Critical Smart Contract bug reports are further capped at 10% of economic damage, which primarily takes into consideration the funds at risk but may include branding and PR aspects at the discretion of the team. However, they have a minimum reward of USD 100 000.

Payouts are handled by the Polygon team directly and are denominated in USD. However, payouts are done in MATIC. The Polygon team may, at its discretion, allow for other options to be done.

Smart Contract

Websites and Applications

The list of all deployed contracts can be found at: https://static.matic.network/network/mainnet/v1/index.json

Only those in the Assets that are actually live and in-use are considered as in-scope of the bug bounty program. In the case of Smart Contracts, please always make sure the code has been deployed and present in the JSON file on the first row.

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. The final classification however takes into consideration the likelihood of the impact being achieved based on the table below. When submitting a bug report, select the original assigned impact level, but please be aware that its severity level may be reassigned based on the likelihood according to this table.

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