In the Treasury contract, the allocateFunds
function overwrites previous allocations instead of updating them, leading to potential loss of allocation history and incorrect fund tracking.
Vulnerable code:
Previous allocations are lost without any record
No tracking of cumulative allocations
Potential for accounting errors
Loss of allocation history
Difficulty in auditing allocation patterns
Could lead to double-spending or under-allocation of funds
Add this test script to the Fund Allocation test script in test/unit/core/collectors/Treasury.test.js
Add cumulative allocation tracking:
Add allocation adjustment functionality:
Manual code review
Foundry Testing Framework
Static analysis
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.