Submission Details
Severity:
Inconsistent State Managment
Summary
The withdraw function doesn't properly validate state conditions
Vulnerability Details
Missing checks for:
Campaign completion status
Deadline conditions
Contribution refunds
Impact
Could allow unauthorized withdrawals or fund loss
Proof Of Concept
// Example of unauthorized withdrawal
// 1. Campaign deadline passes
// 2. Some contributors request refunds
// 3. Creator withdraws remaining funds
// Result: Contributors lose money
Tools Used
Manual review
Recommendations
Implement comprehensive state validation:
pub fn withdraw(ctx: Context<FundWithdraw>) -> Result<()> {
let fund = &ctx.accounts.fund;
require_keys!(
fund.amount_raised > 0,
ErrorCode::InvalidState,
"No funds to withdraw"
);
require_keys!(
fund.deadline == 0 || fund.deadline < Clock::get().unwrap().unix_timestamp as u64,
ErrorCode::InvalidState,
"Deadline not reached"
);
// ... rest of function
}
Rewards breakdown
nSLOC
170This contest has a flat reward structure with the following payouts:
100 EXP
20 EXP
2 EXP
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.