Aragon client smart contracts bug bounty
A bug bounty for the smart contracts in the Aragon client is now live. We intend for hackers to look for smart contract vulnerabilities in our system that can lead to loss of funds or locked DAOs.
Vulnerability reports will be scored using the CVSS v3 standard. The reward amounts for different types of vulnerabilities are:
Critical (CVSS 9.0 - 10.0)
$5,000 - $50,000
Major (CVSS 7.0 - 8.9)
$2,500 - $5,000
Medium (CVSS 4.0 - 6.0)
$1,000 - $2,500
Low (CVSS 1.0 - 3.9)
$500 - $1,000
Rewards will be awarded at the sole discretion of the Aragon Association. Quality of the report and reproduction instructions can impact the reward. Rewards are denominated in USD and will be paid out in ETH.
For this initial bug bounty program, there is a maximum bounty pool of $250,000.
The bug bounty program is ongoing and has ran since October 17th, 2018.
Reporting a found vulnerability
Please responsibly disclose any findings to the development team. You may find instructions on how to do so in the security overview page.
Failure to do so will result in a finding being ineligible for any bounties.
In scope for the bug bounty are all the smart contract components of the Aragon client. They can be found on three main repositories:
Smart contract framework and the core of the system.
- Solidity code under the
aragon-apps (on the master branch)
Contracts for Aragon apps developed by the Aragon Association and are installed by default in most Aragon organizations.
- Solidity code under
MiniMe Token (Aragon fork) (on the master branch)
Governance token deployed for most Aragon organizations.
- Solidity code under the
On-chain deployment templates for Aragon DAOs.
- Solidity code in the
You can find their deployed addresses on live networks in our deployment documentation.
Out of scope
What we consider out of scope for this bug bounty
- Side-effects of properly authenticated smart contract upgrades or contract upgrades that change the storage layout of a contract.
- Revocation of permissions or completely changing how a DAO operates due to important permission being granted through the proper processes.
- Any frontend applications or client-side code interacting with the contracts, as well as testing code.
- Mismatch of the functionality of the contracts and outdated spec documents.
Areas of interest
These are some examples of vulnerabilities that would be interesting
- Bypassing ACL rules to get unauthorized access to an app.
- A user of an app performing an action that could freeze or lock the contract.
- Being able to escalate permissions using the Voting app or Token Manager without a proper vote being successful.
Documentation and resources for hackers
Terms for eligible bounties
- Only unknown vulnerabilities will be awarded a bounty; in case of duplicate reports, the first report will be awarded the bounty.
- Public disclosure of the vulnerability, before explicit consent from Aragon to do so, will make the vulnerability ineligible for a bounty.
- Attempting to exploit the vulnerability in a public Ethereum network will also make it ineligible for a bounty.