pNetwork

Submit a Bug
27 December 2021
Live since
Yes
KYC required
$1,000,000
Maximum bounty

Program Overview

pNetwork is a multi-chain routing protocol for DeFi, NFTs and gaming. It enables assets and data to move frictionlessly from one blockchain to another with support on some of the largest and widely-recognized DeFi platforms today. Currently, the protocol powers cross-chain connections among 12 different blockchains and Layer 2 solutions such as wrapped Bitcoin on Ethereum.

pNetwork is a progressively decentralized protocol home to the pNetwork DAO, pNetwork nodes and the ecosystem’s governance token PNT.

To know more about pNetwork, visit https://p.network/ or join the community at https://twitter.com/pNetworkDeFi

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

  • Thefts and freezing of principal of any amount
  • Thefts and freezing of unclaimed yield of any amount
  • Theft of governance funds
  • Forging data returned by pNetwork nodes before it gets presented to the user by the dapp (XSS)

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.

Critical vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum of USD 50 000 for Critical bug reports.

The following is a known issue that is considered as out of scope. There is an "unhandled exception" (which is on the list of vulnerabilities) in the ERC777; Namely that the ERC777 tokens received hook combined with a tag for automatic peg-in on sends can fail if the user ABI encodes the other information incorrectly. This will revert but with no reason because there's no way to catch the error to add a message.

pNetwork requires KYC to be done for all bug bounty hunters submitting Critical bug reports and wanting a reward. The information needed is an ID photo together with a selfie. Reports for other severity levels do not require any KYC.

Payouts are handled by the pNetwork team directly and are denominated in USD. However, payouts are done in PNT or USDC, up to the discretion of the team.

Smart Contracts and Blockchain

Critical
Level
Up to USD $1,000,000
Payout
high
Level
USD $30,000
Payout
medium
Level
USD $10,000
Payout
low
Level
USD $3,000
Payout

Web and Apps

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

Assets in Scope

All smart contracts of pNetwork can be found at https://github.com/provable-things. 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/Blockchain

  • Thefts and freezing of principal of any amount
  • Thefts and freezing of unclaimed yield of any amount
  • Theft of governance funds
  • Firing of Redeem event without pegging out funds (PToken.sol)
  • Firing of PegIn event without pegging in funds (Erc20Vault.sol)
  • Re-entrancy attacks when pegging in or out (PToken.sol & Erc20Vault.solt)
  • Receiving greater than the amount pegged in or out (PToken.sol & Erc20Vault.sol)
  • Receiving fewer tokens than the amount pegged in or out (PToken.sol & Erc20Vault.sol)
  • Pegging in or out non-supported tokens.

Web/App

  • Forging data returned by pNetwork nodes before it gets presented to the user by the dapp (XSS)
Smart Contract - pERC20-on-bsc - native-vault-address
Type
Smart Contract - pERC20-on-telos - native-vault-address
Type
Smart Contract - pERC20-on-eos - native-vault-address
Type
Smart Contract - pERC20-on-ultra - native-vault-address
Type
Smart Contract - pERC20-on-polygon - native-vault-address
Type
Smart Contract - pEOS-on-eth - host-smart-contract-address
Type
Smart Contract - IQ-on-eth - host-smart-contract-address
Type
Smart Contract - pVAI-on-eth - host-smart-contract-address
Type
Smart Contract - WSB-on-eth - host-smart-contract-address
Type
Smart Contract - TLOS-on-eth - host-smart-contract-address
Type
Smart Contract - pERC20-on-xdai - native-vault-address
Type
Smart Contract - EFX-on-eth - host-smart-contract-address
Type
Smart Contract - pSEEDS-on-eth - host-smart-contract-address
Type
Smart Contract - OCP-on-eth - host-smart-contract-address
Type
Smart Contract - pSAFEMOON-on-eth - host-smart-contract-address
Type
Smart Contract - ORE-on-eth - host-smart-contract-address
Type
Smart Contract - TransparentUpgradeableProxy
Type
Smart Contract - ERC20Vault
Type
Smart Contract - AdminUpgradeabilityProxy
Type
Smart Contract - pBEP20-on-polygon - native-vault-address
Type
Smart Contract - pBEP20-on-eth - native-vault-address
Type
Smart Contract - pSFM-on-eth - native-vault-address
Type
Smart Contract - ZMT-on-bsc - host-smart-contract-address
Type
Smart Contract - BIST-on-bsc - host-smart-contract-address
Type
Smart Contract - pOPEN-on-bsc - host-smart-contract-address
Type
Smart Contract - GALA-on-bsc - host-smart-contract-address
Type
Smart Contract - TLOS-on-bsc - host-smart-contract-address
Type
Smart Contract - ANRX-on-bsc - host-smart-contract-address
Type
Smart Contract - PNT-on-bsc - host-smart-contract-address
Type
Smart Contract - pOPIUM-on-bsc - host-smart-contract-address
Type
Smart Contract - pdefiplusplus-on-bsc - host-smart-contract-address
Type
Smart Contract - pBCP-on-bsc - host-smart-contract-address
Type
Smart Contract - PTERIA-on-bsc - host-smart-contract-address
Type
Smart Contract - CGG-on-bsc - host-smart-contract-address
Type
Smart Contract - EFX-on-bsc - host-smart-contract-address
Type
Smart Contract - AdminUpgradeabilityProxy
Type
Smart Contract - TransparentUpgradeableProxy
Type
Smart Contract - pEOS-on-polygon - host-smart-contract-address
Type
Smart Contract - PNT-on-polygon - host-smart-contract-address
Type
Smart Contract - TransparentUpgradeableProxy
Type
Smart Contract - TFF-on-polygon - host-smart-contract-address
Type
Smart Contract - USDO-on-polygon - host-smart-contract-address
Type
Smart Contract - AdminUpgradeabilityProxy
Type
Smart Contract - TransparentUpgradeableProxy
Type
Smart Contract - PNT-on-xdai - host-smart-contract-address
Type
Smart Contract - Vault EOS-like
Type
Smart Contract - pToken EOS-like
Type
Web/App
Type

Prioritized Vulnerabilities

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)

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)

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