The SystemConfig::updateReferrerInfo()
function allows any user to update the referrer settings for any address without proper access control. This means that an unauthorized user could modify the referrer and rates for another user.
The updateReferrerInfo
function currently validates that the _msgSender()
is not the same as the _referrer
, but it does not restrict who can call the function or update the referrer information for a given address. So This lack of access control allows any external caller to modify the referral information, including the referrer address and associated rates, for any user.
https://github.com/Cyfrin/2024-08-tadle/blob/main/src/core/SystemConfig.sol#L41-L80
The absence of proper access control allows unauthorized users to update referral information, which could lead to manipulation of the referral system or Malicious users could change the referrer address for another user, diverting referral rewards to themselves or others.
Manual Review
Introduce a modifier to restrict access to the updateReferrerInfo function.
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.