KogeFarm

KogeFarm is a low-fee, multi-chain yield aggregator/optimizer that automates reward harvesting and yield compounding across hundreds of farms from dozens of yield farm platforms. It was launched in May 2021 on the Polygon chain and is quickly expanding to others.

For more information about KogeFarm, please visit https://kogefarm.io/vaults.

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

• Loss of user funds staked (principal) by freezing or theft

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

The following vulnerabilities are not eligible for a reward: Small difference between principal and vault shares due to rounding to 10^18 decimals.

In addition to Immunefi’s Vulnerability Severity Classification System, KogeFarm classifies the following vulnerabilities as follows. In case of discrepancy, the one below will be followed.

Critical

• Theft of principal is critical if the possible theft is greater than USD 100000.
• Freezing of principal is critical if it cannot be unfrozen, with impacted amounts greater than USD 100000.

KogeFarm requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is the bug bounty hunter's face and document verification using https://kycaid.com/. The collection of this information will be done by the KogeFarm team.

Payouts are handled by the KogeFarm team directly and are denominated in USD. However, payouts are done in USDC.

In the Github link in the Assets in Scope table, only Exact Match Verified smart contracts are considered as in-scope of 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 Contracts/Blockchain

• Loss of user funds staked (principal) by freezing or theft

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

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

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