Polygon

Polygon provides the core components and tools to join the new, borderless economy and society. With Polygon, any project can easily spin-up a dedicated blockchain network which combines the best features of stand-alone blockchains (sovereignty, scalability and flexibility) and Ethereum (security, interoperability and developer experience). Additionally, these blockchains are compatible with all the existing Ethereum tools (Metamask, MyCrypto, Remix etc), and can exchange messages among themselves and with Ethereum.

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

This bug bounty program is focused on their smart contracts and apps and is focused on 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. 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.

A PoC and a suggestion for a fix is required for all Critical and High bug reports. Additionally, a PoC is required for Medium Web/App 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 ETH, MATIC, or a stablecoin, at the discretion of the Polygon team.

Only the web/app assets explicitly listed here are in-scope. All else is out-of-scope.

Relevant smart contracts of Polygon can be found at:

https://github.com/maticnetwork/contracts

https://github.com/maticnetwork/pos-portal

https://github.com/fx-portal/contracts

https://github.com/maticnetwork/genesis-contracts

However, 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.

Smart Contracts

• 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

Web/App

• Domain takeover
• Denial of service
• Access on server
• Users spoofing other users
• Redirected funds by address modification

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

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

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)

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

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