There is a flaw in updateReferrerInfo that allows anyone to change another user's referralInfo and set the target's referrer to himself.
In updateReferrerInfo, there are two key points:
It only requires _msgSender() != _referrer, the subsequent part has nothing to do with _msgSender.
The info being set is referralInfoMap[_referrer], and referralInfo.referrer = _referrer
This leads to anyone other than _referrer being able to change his referrerRate and authorityRate, and his referrer can only be himself.
https://github.com/Cyfrin/2024-08-tadle/blob/main/src/core/SystemConfig.sol#L41-L72
This allows anyone to change another user's referralInfo and set the target's referrer to himself.
The referrerRate and authorityRate are used to distribute referrer bonus, and this vulnerability allows anyone to influence the amount of bonus distributed.
vscode
I think ReferralInfo storage referralInfo = referralInfoMap[_referrer];-> ReferralInfo storage referralInfo = referralInfoMap[_msgSender()];is right.
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.