Decentraland

Submit a Bug
05 July 2022
Live since
Yes
KYC required
$500,000
Maximum bounty
13 October 2022
Last updated

Program Overview

Decentraland is a decentralized virtual social platform powered by the Ethereum blockchain. Within the Decentraland platform, users can create, experience, and monetize content and applications. Decentraland is built, governed, and owned by its users. Through the decentralized autonomous organization (DAO) users can submit proposals for owners of MANA and LAND to vote on.

For more information about Decentraland, please visit https://decentraland.org/.

Rewards by Threat Level

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

High smart contract vulnerabilities to be calculated as 0.1% of the economic damage and capped at USD 500,000, 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 20,000.

All other rewards for the bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. However, there is a minimum reward of USD 1 000 for each severity level, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.

Decentraland has combined Critical and High Smart Contract impacts together, please refer to the High Smart Contract rewards and impacts respectively.

The following vulnerabilities are not eligible for a reward:

Decentraland requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are Name, Mailing Address and any ID. The collection of this information will be done by the Decentraland team.

Payouts are handled by the Decentraland team directly and are denominated in USD. However, payouts are done in MANA and USDT, with a minimum of 20% to be done in USDT.

Smart Contract

High
Level
Up to USD $500,000
Payout
PoC Required
Medium
Level
Up to USD $20,000
Payout
PoC Required
Low
Level
USD $1,000
Payout
PoC Required

Websites and Applications

Critical
Level
Up to USD $18,000
Payout
PoC Required
High
Level
Up to USD $6,000
Payout
PoC Required
Medium
Level
Up to USD $3,000
Payout
PoC Required
Low
Level
USD $1,000
Payout
PoC Required

Assets in scope

All smart contracts of Decentraland can be found at https://github.com/decentraland. 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 Decentraland 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.

Bug reports from compensated team members of any Decentraland core units will not be eligible for a reward. Employees and team members of third-party suppliers to core units that operate in a technical capacity and have assets covered in this bug bounty program will also not be eligible for a reward. All team members of the audit companies Decentraland works with, and its third-party suppliers, including Immunefi itself and its subsidiaries, are not eligible for a reward.

Bug reports from team members and third-party suppliers of businesses and organizations that are not a Decentraland Core Unit but have assets considered as critical infrastructure covered under the bug bounty program are also not eligible for 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 Contract

  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
    High
    Impact
  • Transaction & meta transactions replay attacks
    High
    Impact
  • Undesired destruction or burning of assets: wearables
    High
    Impact
  • Minting assets from unauthorized addresses
    High
    Impact
  • Temporary freezing of funds/assets for any amount of time
    Medium
    Impact
  • Controlled loss of user assets
    Medium
    Impact
  • Unbounded gas consumption that lead to make the core contract functionality unusable
    Medium
    Impact
  • Smart contract fails to deliver promised returns, but doesn’t lose value
    Low
    Impact
  • Reentrancy or frontrunning attacks with no users assets loss involvement but lead to an undesired product behaviour by design
    Low
    Impact

Websites and Applications

  • Execute arbitrary system commands
    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 down the application/website
    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, commenting, voting, making trades, withdrawals, etc.
    Critical
    Impact
  • Direct theft 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
  • Access/Exploitation of user wallets/assets via the web application.
    Critical
    Impact
  • Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.
    High
    Impact
  • Changing sensitive details of other users (including modifying browser localStorage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.
    High
    Impact
  • Improperly disclosing confidential user information such as email address, phone number, physical address, etc.
    High
    Impact
  • Subdomain takeover of decentraland.org
    High
    Impact
  • XSS Attacks or any other DOMbased user exploits.
    High
    Impact
  • Escape sandbox attack from scenes (injection of HTML or code injections in main thread from deployed scene code)
    High
    Impact
  • Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data
    Medium
    Impact
  • Redirecting users to malicious websites without their consent (Open Redirect)
    Medium
    Impact
  • Catalyst Content: impersonation, hijack, DoS (excluding distributed and botnet-like attacks)
    Medium
    Impact
  • Platform stability: DoS (excluding distributed and botnet-like attacks) and Server degradation
    Medium
    Impact
  • XSRF Attacks
    Medium
    Impact
  • Cache poisoning
    Medium
    Impact
  • Changing non-sensitive details of other users (including modifying browser localStorage) with/without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or disabling notification
    Low
    Impact
  • Any impact involving a publicly released CVE
    Low
    Impact
  • Taking over broken or expired social media links previously owned oficially by The Decentraland Foundation
    Low
    Impact
  • Temporarily disabling user to access target site and can’t be solve by log-in again, such as locking up the victim from login, cookie bombing, etc.
    Low
    Impact

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
  • Frontrunning, including backrunning and sandwich attacks that may not lead to user funds or assets
  • Bugs in dependencies (unless they lead to equivalently direct attacks on Wormhole)
  • Any secret data checked into the repository. Such as API/AUTH tokens

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
  • Attacks requiring privileged access from within the organization
  • Crashes in play.decentraland.org or scene preview
  • Software defects in deployed scenes in play.decentraland.org
  • Issues related to scene code itself
  • Scenes deployed by users using malicious code that requires users to download or interact with it
  • Any vulnerability that requires the user to input commands in the browser console

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