Party DAO - D1r3Wolf's results

Protocol for group coordination.

General Information

Platform: Code4rena

Start Date: 31/10/2023

Pot Size: $60,500 USDC

Total HM: 9

Participants: 65

Period: 10 days

Judge: gzeon

Total Solo HM: 2

Id: 301

League: ETH

PartyDAO

Findings Distribution

Researcher Performance

Rank: 39/65

Findings: 1

Award: $152.37

🌟 Selected for report: 0

🚀 Solo Findings: 0

Findings Information

🌟 Selected for report: TresDelinquentes

Also found by: 3docSec, Arz, Bauchibred, D1r3Wolf, J4X, Neon2835, Pechenite, adeolu, chainsnake

Labels

bug
2 (Med Risk)
downgraded by judge
satisfactory
insufficient quality report
duplicate-127

Awards

152.3655 USDC - $152.37

External Links

Lines of code

https://github.com/code-423n4/2023-10-party/blob/main/contracts/crowdfund/ETHCrowdfundBase.sol#L247-L258

Vulnerability details

Impact

A case is missing in the minContribution check, which will cause the DoS for crowd fund finalization and party creation. A case where, totalContributions is near minTotalContributions, and (maxTotalContributions - totalContributions) < minContribution. In that case, even though users are willing to give fund, no one can contribute and even host cant do anything. They just need to wait for expiration and create the initiate the new crowdfund, which disrupts the totalContribution. The next time might not acheive the same contribution again.

Proof of Concept

Lets take, minTotalContributions = 90, maxTotalContributions = 100. minContribution = 15, maxContribution = 25. Now the totalContributions = 89, just 1 less than to minTotalContributions.

Since the amount is getting reduced based on the (maxTotalContributions - totalContributions), the amount can't exceed the 11 (100 -89). But the minContribution check will fail since 11 < 15. It will create DoS

Modify the minContribution check, or else add a constraint of minContribution <= (maxTotalContributions - minContribution) at initiation to avoid this deadlock.

Assessed type

DoS

#0 - c4-pre-sort

2023-11-12T07:43:13Z

ydspa marked the issue as duplicate of #552

#1 - c4-pre-sort

2023-11-12T07:43:17Z

ydspa marked the issue as insufficient quality report

#2 - c4-judge

2023-11-19T14:33:03Z

gzeon-c4 marked the issue as unsatisfactory: Invalid

#3 - c4-judge

2023-11-19T14:40:13Z

gzeon-c4 marked the issue as unsatisfactory: Out of scope

#4 - c4-judge

2023-11-23T14:16:10Z

gzeon-c4 marked the issue as unsatisfactory: Out of scope

#5 - c4-judge

2023-11-23T14:16:57Z

gzeon-c4 changed the severity to 2 (Med Risk)

#6 - c4-judge

2023-11-23T14:20:29Z

gzeon-c4 marked the issue as satisfactory

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