NFTfi (Testnet Refi)-logo

NFTfi (Testnet Refi)

NFTfi is the leading liquidity protocol for NFTs. NFTfi allows NFT owners to use the assets (NFTs) they own to access the liquidity they need by receiving secured loans from liquidity providers, peer-to-peer, in a completely trustless manner.

NFT
Lending
Solidity
Maximum Bounty
$20,000
Live Since
17 January 2024
Last Updated
09 November 2024
  • PoC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - Refinancing.sol
Added on
17 January 2024
Target
Type
Smart Contract - RefinancingAdapter.sol
Added on
17 January 2024

Impacts in Scope

Impacts that depend on NFTfi registering faulty NFT Adapters, Refinancing adapters, NFT collections or ERC20 loan denominations are out of scope. That is, only impacts in the scope of currently registered and enabled adapters, NFT collections and loan denominations.

Severity
Critical
Title

Theft or permanent freezing of NFT loan collateral during the Refinancing process of paying off the old loan and refinancing to a new loan.

Severity
Critical
Title

Direct theft or permanent freezing of any lender or borrower funds during the Refinancing process of paying off the old loan and refinancing to a new loan.

Out of scope

Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • 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
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers