Caller does not get referral info about himself due to incorrect logic of updateReferrerInfo().
As a result, referral bonus fund transfers will be handled incorrectly.
User calls updateReferrerInfo() to update referral settings for himself. The caller can set a new referral rate and authority rate for himself.
The user is unable to update _referr to his/her referrer because he/she updates the value of referralInfoMap[_referr], not referralInfoMap[msg.sender].
Therefore, several problems may occur.
For example look at createTaker().
As you can see, caller uses systemConfig.getReferralInfo() to get referral Info about himself.
But caller does not get referral info about himself due to incorrect logic of updateReferrerInfo().
As a result, fund transfers will be handled incorrectly.
Caller does not get referral info about himself due to incorrect logic of updateReferrerInfo().
As a result, Referral Bonus fund transfers will be handled incorrectly.
Mannual Review
updateReferrerInfo() is modified as follow.
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.