Ocean Protocol

Ocean Protocol unlocks the value of data.

Data owners and consumers use the Ocean Market app to publish, discover, and consume data in a secure, privacy-preserving fashion. OCEAN holders stake liquidity to data pools.

Developers use Ocean libraries to build their own data wallets, data marketplaces, and more.

Ocean datatokens wrap data services as industry-standard ERC721 NFTs and ERC20 tokens. This enables data wallets, data exchanges, and data co-ops by leveraging crypto wallets, exchanges, and other decentralized finance (DeFi) tools.

Special Case: For this specific bounty program, the Ocean Protocol Foundation is allowing testing on their public testnets.

For more information about Ocean Protocol, please visit https://oceanprotocol.com/.

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

• Bugs that could result in funds being lost
• Permanent freezing of funds
• Unauthorized protocol changes (e.g. to fees)

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2. 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 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. For this specific bounty program, the Ocean Protocol Foundation is allowing testing on their public testnets.

All known issues highlighted in the github repo and audit report below are considered as out of scope:

• https://github.com/oceanprotocol/contracts/issues
• https://github.com/oceanprotocol/contracts/blob/v4main/docs/Ocean_Protocol_Smart_Contract_Security_Audit_Report_Halborn_Final%20(1).pdf

The Ocean Protocol Foundation does not require KYC to be done for this program. However, bug bounty hunters submitting a report and wanting a reward will have to provide an invoice submitted via the Request invoicing platform. The invoice needs to include the details below:

• Email address
• Invoice date
• Country
• Description of bug bounty
• Granted amount (OCEAN)
• Payment details - crypto-wallet address

Payouts are handled by the Ocean Protocol Foundation team directly and are denominated in USD. However, payouts are done in OCEAN.

Smart Contract

Websites and Applications

All smart contracts of Ocean Protocol can be found at https://github.com/oceanprotocol/contracts/tree/v4main. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

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)
• Bugs already identified in external third-party audits. (OPF will publish when available).
• Known Issues that are already caught on the repo issues/PRs
• Issues reported on other branch than main
• Public deployments of the above repos. Deployments can be used as helpers, but penetration tests or similar are out of scope. Purpose of the bounty is to test the code in the repo.
• Compute2Data in market is WIP, so currently out of scope. This paragraph will be updated when full C2D support is ready.

Smart Contracts and Blockchain

• Natural network activity (e.g. swapping datatokens or adding liquidity to datatoken pools) whose involved mechanisms could result in unprofitable actions for the particular stakeholder (e.g. slippage, impermanent loss)
• Attacks related to multisig governance of addresses that control protocol changes
• Frontrunning, backrunning, sandwich attacks, and related known MEV attacks
• 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:

• 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