The updateReferrerInfo function contains several critical vulnerabilities that can lead to incorrect behavior, unauthorized updates, and potential exploitation.
updateReferrerInfofunction allows the update of the refferalInfoof any referrer by any user.
https://github.com/Cyfrin/2024-08-tadle/blob/main/src/core/SystemConfig.sol#L69-L72
Due to this, any user can update the referrerInfoof other users and set themselves as a referrer. referrerInfois accessed in createTakerfunction where it sends some fees to referrerof the taker.
https://github.com/Cyfrin/2024-08-tadle/blob/main/src/core/PreMarkets.sol#L199-L201
Any user can update the referrerInfoof other users and set themselves as a referrer. referrerInfois accessed in createTakerfunction where it sends some fees to referrerof the taker.
Manual review
User should only be able to update referralInfofor themselves and not other users. Fixed code in updateReferrerInfofunction.
Valid high severity. There are two impacts here due to the wrong setting of the `refferalInfoMap` mapping. 1. Wrong refferal info is always set, so the refferal will always be delegated to the refferer address instead of the caller 2. Anybody can arbitrarily change the referrer and referrer rate of any user, resulting in gaming of the refferal system I prefer #1500 description the most, be cause it seems to be the only issue although without a poc to fully describe all of the possible impacts
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.