Chainlink

Chainlink is the industry standard for building, accessing, and selling oracle services needed to power hybrid smart contracts on any blockchain. Chainlink oracle networks provide smart contracts with a way to reliably connect to any external API and leverage secure off-chain computations for enabling feature-rich applications. Chainlink currently secures tens of billions of dollars across DeFi, insurance, gaming, and other major industries, and offers global enterprises and leading data providers a universal gateway to all Blockchains.

Learn more about Chainlink by visiting chain.link or reading the developer documentation at docs.chain.link. To discuss an integration, reach out to an expert.

Unlike other bug bounty programs on Immunefi, all bug report submissions, including associated vulnerabilities, become the exclusive property of Chainlink Labs. By making a submission to this program and in consideration for a bounty, the bug submitter conveys all ownership rights, titles, and interests in the bug report to Chainlink Labs. Thus, the final decision on whether a postmortem will be written is at the sole discretion of Chainlink Labs.

By submitting a bug report, you agree to refrain from any public disclosure of the report and associated vulnerability unless explicit written consent is provided in advance by the Chainlink team.

Use testnet oracles: https://docs.chain.link/docs/any-api/testnet-oracles/#:~:text=test

Instructions to setup your node: https://docs.chain.link/chainlink-nodes/#:~:text=node

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 Smart Contracts bug reports require a PoC and a suggestion for a fix to be eligible for a reward. All Websites and Applications bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Rewards for “Critical” Smart Contract vulnerabilities are at the sole and exclusive discretion of Chainlink Labs, with a minimum reward of USD $100,000 and maximum reward of USD $3,000,000. Determination of the final reward amount may take into consideration, but is not limited to, the following factors: funds at risk, as well as public relations and branding aspects.

KYC requirement

To ensure compliance with applicable law, Chainlink Labs requires Know-Your-Customer (KYC) information to be provided for all bug bounty hunters submitting a report and requesting a reward.

The information required are: Full Name (First and Last Names, plus any middle initial, prefix, and/or suffix) City, Country of Residence Country of Citizenship Wallet Address (for transfer of payment)

The collection and review of this information will be handled by the Chainlink Labs team directly.

Payouts are handled by the Chainlink Labs team directly, denominated in USD, and sent in Ethereum (ETH), USD Coin (USDC), or Tether (USDT).

Smart Contract

Websites and Applications

All EVM smart contracts of Chainlink can be found at https://github.com/smartcontractkit/chainlink/tree/master/contracts. The list of all deployed contracts can be found at https://docs.chain.link/docs/data-feeds/price-feeds/addresses/. However, only those in the Assets in Scope table are considered to be in-scope of the bug bounty program. *.smartcontract.com assets, test code, files in dev folders, and files with XXX are out of scope for this bug bounty program.

If an impact can be caused to any other asset managed by Chainlink 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.

Contracts or code present in dev/test directories or files with xxx in their name are not eligible for rewards.

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)
• Mentions of secrets, access tokens, API keys, private keys, etc. in Github, will be considered out of scope without proof that they are in-use in production

Smart Contracts

• 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
• 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

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
• Disclosure of vulnerabilities will require the approval of the Chainlink team