Rigor Protocol contest - ayeslick's results

Community lending and instant payments for new home construction.

General Information

Platform: Code4rena

Start Date: 01/08/2022

Pot Size: $50,000 USDC

Total HM: 26

Participants: 133

Period: 5 days

Judge: Jack the Pug

Total Solo HM: 6

Id: 151

League: ETH

Rigor Protocol

Findings Distribution

Researcher Performance

Rank: 103/133

Findings: 1

Award: $40.62

🌟 Selected for report: 0

🚀 Solo Findings: 0

HomeFi the setAddr function Admin will not be able to reset the variables to new addresses should something happen and the address needs to be updated.

Recommendation: Allow admin to set the addresses under certain circumstances. Perhaps through a DAO vote.

HomeFi setTrustedForwarder function doesn’t prevent the address from being set to address(0).

Recommendation: Use the nonZero modifier when setting addresses

Project initialize function doesn’t prevent addresses from being set to address(0).

Recommendation: Check addresses to make sure they aren’t the zero address.

checkSignatureValidity:

Anyone can use other callers approvedHashes.

For example, the Community contracts’ escrow function. An operator waits until the builder and lender both call approveHash. If they do not use it immediately an operator could use it for them in a grief attack.

Recommendation: Remove the approvedHashes mapping and rely solely on the _recoveredSignature.

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