When an extra rate is added to a referrer, then the function SystemConfig.updateReferrerInfo can be called by anyone (other than the referrer) to adjust the _referrerRate and the _authorityRate within those bounds.
The SystemConfig.updateReferrerInfo function has no checks on who is calling apart from making sure the caller isn't the referrer themselves.
The bonus that a referrer gets when an action happens they have referred depends on the values of _referrerRate. If the referrer has been awarded an extra rate, then this can be taken off the referrer when the bonus is caluclated and sent somewhere else based on the authorityReferrer instead.
This can be seen by adding this setup to the test_ask_turbo_chain function in the test script PreMarkets.t.sol.
Manual review + foundry
Lock down the function so that it is not publiclly executable.
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.