In the contribute
function when a new contributioin record is iitialized, the contribution amount is incorrectly set to a hardcoded value of '0' instead of the user-provided amount
parameter.
When a User contributes to a fund for the first time, the protocol initializes a new contributioin record to track their contribution. However, the amount
field in this record is set to '0' rather than the actual contribution amount. The Actual Bug raises when the User Tries to refund the amount which was contributed. Because of having 0 in the contributioin.amount
the user will get nothing if the User tries to refund
the sol. The User funds will be lost.
User A will contribute 5 sol to the Fund_x Account.
The User A contribution will be stored as 0 instead of 5 sol.
Now if the User tries to refund the sol. User will get nothing due to the fact that the user.contribution
variable is set to '0'.
User successfully Lost his Sol.
High
Manual Review
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.