OpenZeppelin

As the premier crypto cybersecurity technology and services company, we’ve built OpenZeppelin Contracts with our best security practices. We are committed to ensuring the utmost security in our community-vetted smart contracts, and our bounty program provides rewards of up to $25,000 USD for reporting critical vulnerabilities in our smart contracts library. This bug bounty program is focused on OpenZeppelin Contracts and mainly intends to prevent:

• Loss of funds by freezing another user’s funds, or theft of another user’s funds
• Permanent denial of service (smart contract is made unable to operate)
• Access control bypass, including privilege escalation
• Smart contract not behaving as intended

This is an overlay bug bounty program for OpenZeppelin’s Contracts library. A vulnerability in an OpenZeppelin contract would likely affect many other projects and could trigger various other bounties. This program would be potentially additive to those cases.

OpenZeppelin may issue GHSA/CVEs for reported vulnerabilities and will offer to credit issue reports in those public reports.

Primacy of Impact vs Primacy of Rules

OpenZeppelin adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.

Previous Audits

OpenZeppelin’s completed audit reports can be found at OpenZeppelin Contracts’ Security Center while previous security advisories are available at GHSA/CVEs. OpenZeppelin will offer to credit issue reports in those public reports. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.

Feasibility Limitations

OpenZeppelin will assess likelihood depending on the complexity of the steps involved in its execution and the exposure created by the vulnerability, as well as impact depending on the assets or systems at risk, capped to the worst-case impacted instance using the affected code.

OpenZeppelin will evaluate the vulnerability of the affected code considering whether the issue arises directly from the library code while used as provided or if it requires a custom user implementation. Determining the likelihood of exploit on custom implementations will depend on how likely a library user is to make such an implementation and how common is the pattern leading to it.

For example, if a data structure can be cleared by any caller of a smart contract, its likelihood will be high if it holds user balances, although, if the vulnerability allows overriding non-critical values such as an already executed governor proposal flag, its likelihood will be low but can escalate to medium if it comes with side effects that increase the incentives of exploitation (e.g. proposal re-execution).

Similarly, if an instance of an AccessManager can be made unusable, its impact will be high but could be lowered to medium if the attacker requires special permissions in the system, and finally, it will be considered low if the contract is frozen only during 1 block before a threshold is met.

The final threat level will be decided based on the matrix above. For a vulnerability with low impact, if its likelihood is high because the cost of exploiting a single instance is negligible, then its final threat level will be medium severity.

Immunefi Standard Badge

By adhering to Immunefi’s best practice recommendations, OpenZeppelin has satisfied the requirements for the Immunefi Standard Badge.

KYC Requirements

OpenZeppelin’s bug bounty program requires an invoice to be submitted and a KYC screen to be performed prior to OpenZeppelin providing a bug bounty reward. Once a payout is confirmed, a member of OpenZeppelin will reach out to you directly to collect the necessary information, including:

• Full Legal Name
• Email Address
• Mailing Address
• Wallet Address (Ethereum Mainnet Only)