Nibbl contest - Treasure-Seeker's results

NFT fractionalization protocol with guaranteed liquidity and price based buyout.

General Information

Platform: Code4rena

Start Date: 21/06/2022

Pot Size: $30,000 USDC

Total HM: 12

Participants: 96

Period: 3 days

Judge: HardlyDifficult

Total Solo HM: 5

Id: 140

League: ETH

Nibbl

Findings Distribution

Researcher Performance

Rank: 83/96

Findings: 1

Award: $28.28

🌟 Selected for report: 0

🚀 Solo Findings: 0

Lines of code

https://github.com/code-423n4/2022-06-nibbl/blob/8c3dbd6adf350f35c58b31723d42117765644110/contracts/Proxy/ProxyVault.sol#L56 https://github.com/code-423n4/2022-06-nibbl/blob/8c3dbd6adf350f35c58b31723d42117765644110/contracts/NibblVault.sol#L585

Vulnerability details

Impact

The ProxyVault and NibblVault contracts has an empty receive function implementation. This can cause a loss of funds as people may by mistake send the contract some eth, and will never be able to recover this ETH.

Proof of Concept

Easy way to check is try sending the ProxyVault or NibblVault contract some eth. There is no way to now withdraw this ETH (stuck forever)

Tools Used

VS Code

Delete receive function

#0 - mundhrakeshav

2022-06-30T11:14:35Z

The funds in vault are redeemed by users.

#1 - HardlyDifficult

2022-07-03T23:47:55Z

Agree it seems the receive function does not add value and should be removed to prevent user error. But the funds are accounted for in redeem so funds are not lost. Downgrading and converting this into a QA report for the warden.

AuditHub

A portfolio for auditors, a security profile for protocols, a hub for web3 security.

Built bymalatrax © 2024

Auditors

Browse

Contests

Browse

Get in touch

ContactTwitter